SharePoint developers who write software for Microsoft Office SharePoint Server or Windows SharePoint Services will get new features from Visual Studio 2010 according to S. "Soma" Somaseger, senior vice president of the Microsoft developer division.
He wrote in his blog entry, SharePoint tools support in Visual Studio, that Visual Studio would provide two major features:
- Project templates, designers, and deployment infrastructure that will make any .NET developer instantly more productive on the SharePoint platform.
- An extensibility API that will continue to foster the ecosystem of third party developers who create development tools and technologies.
Visual Studio 2010 will support debugging, Intellisense, and statement completion for SharePoint projects. You'll be able to import existing SharePoint content. You'll also be able to quickly navigate and browse your SharePoint site directly in Visual Studio.
We will be able to navigate and browse a SharePoint site directly in Visual Studio 2010 using the Server Explorer but we still have the old problem that is remote SharePoint development, in this version this feature isn’t available, and the reason is the following:
“To achieve the level of scalability SharePoint needs, SharePoint is architected to use one web application to serve many individual sites. That's great for SharePoint's ability to scale, bad for Visual Studio's ability to debug an individual site or customization without adversely affecting other sites or developers using a shared server. In the extreme case, when stopped on a breakpoint in a custom web part for example the site could appear frozen to another developer working in a different area of the site or different site that happens to be part of the same web application.
Addressing that behavior was not something we could accomplish in this product cycle. So we decided it was better to limit our support to the more predictable local development experience.
We're also investing in the ALM experience to better support teams of developers working together on a SharePoint solution (source code control, VSTS team build, etc.). Those investments should make it significantly easier to collaborate on a SharePoint solution, publish the solution to test or staging environments, etc.”
So we will need to have SharePoint installed on our development OS and SharePoint Designer maintains is purpose.
Since we have to installs SharePoint in our developer environment would be great to have a SharePoint version for development client OS like XP or Vista or Windows 7.
For more information, see SharePoint Development with Visual Studio on Channel 9.
