140 likes | 226 Views
The new experience for developing SharePoint solutions in VS2010. Richard Fennell & James Mann from Black Marble. @ RichardFennell. http ://blogs.blackmarble.co.uk/blogs/rfennell http://blogs.blackmarble.co.uk/blogs/jmann. rfennell@blackmarble.co.uk jmann@blackmarble.co.uk.
E N D
The new experience for developing SharePoint solutions in VS2010 Richard Fennell & James Mann from Black Marble @RichardFennell http://blogs.blackmarble.co.uk/blogs/rfennellhttp://blogs.blackmarble.co.uk/blogs/jmann rfennell@blackmarble.co.uk jmann@blackmarble.co.uk
SharePoint development was not easy... • Development OS restrictions • No end to end story • Much use of own or community tools • Choices had to be made to do • on site customisation • or feature packaging
Life is better with Visual Studio 2010... • SP2010 can installed on client OS • Sandbox applications • Templates are provided for most SharePoint artefacts • We get an F5 deployment experience • Interoperability between SharePoint Designer and Visual Studio
Demo Visual Studio 2010
Demo SharePoint Designer
Clients Talking to SharePoint - then In the past we used to call the web services on the Web Tier
ClientsTalking to SharePoint - now We now have a .NET Client API which wrappers the web service calls API
Demo Sharepoint CLIENT APi
Other useful management tools • SharePoint Manager 2010 (CodePlex) • Use to inspect the farm, and edit to a degree. Useful to track down stray content types. • SharePoint 2010 Service Manager (CodePlex) • If running on a development box with less than 8GB can manage what is running to optimise the memory you have.
Other useful development tools • Typemock Isolator (Commercial Product) • Allow faking out of SP object, can be useful to test items such as WebPart without running SharePoint • SP Dispose Checker (MSDN) • Static analysis tool that checks for best practice use of the SharePoint object model
Demo Other Tools
Summary - Our top tips • Target SharePoint 2010 with Visual Studio 2010 • Make sure your WSP work in their simplest form • Make sure your features target the correct scope as altering them is time consuming • Use SharePoint Designer to export ‘spike’ projects • Run SPDispose in your automated builds