Today, developers can use Visual Studio 2005 or Visual Studio 2008 to develop solutions for Microsoft Office SharePoint Server 2007 (MOSS) and Windows SharePoint Services 3.0 (WSS). In addition to the features in VS 2005 and VS 2008, developers can also use Visual Studio Extensions for WSS and dozens of third party tools.
In Visual Studio 2010, we’re going to expand Sharepoint support in two key areas. First, Visual Studio 2010 will deliver a broad set of project templates, designers, and deployment infrastructure that will make any .NET developer instantly more productive on the SharePoint platform. Second, we are exposing an extensibility API that will continue to foster the ecosystem of third party developers who create development tools and technologies.
Visual Studio 2010 will come with a broad set of project and items templates. You’ll be able to use these to quickly create or update SharePoint elements such as list definitions, list instances, site definitions, workflows, event receivers, Business Data Catalog models, and content types.
In Visual Studio 2008, the supported workflow projects could be created only for lists and document libraries. In Visual Studio 2010, you’ll be able to create list and site level workflows as well as create aspx association and initiation forms. And, as you would expect, the new Visual Studio 2010 designers can be used to create Web Parts, application pages, and user controls for a SharePoint site (see screenshot, below.)
Of course, you get all the benefits that you would expect while developing in Visual Studio such as full support for code debugging, Intellisense, and statement completion. The WSP Importer enables you to quickly import existing SharePoint content and project wizards simplify solution development. For example, the wizard for Event Receivers allows you to simply select the events you want to handle and it will generate the necessary code and XML for you. And, you will be able to quickly navigate and browse your Sharepoint site directly in Visual Studio with use the Server Explorer (see screenshot, below.)
Visual Studio 2010 provides a rich set of project templates and tools that developers can use to create custom SharePoint solutions. Although these SharePoint projects and tools work well for many application development scenarios, there are times when different or new functionality is needed. In these cases, you can adapt the SharePoint projects and tools in Visual Studio by using a new Visual Studio extensibility API. The API will let you create new SharePoint project items, automate and extend existing SharePoint project items, enhance deployment and retraction functionality, and extend the display and actions of SharePoint nodes in Server Explorer.
If you’d like to learn even more, you might check out Reza Chitsaz on Channel 9.
Namaste!
PingBack from http://www.anith.com/?p=11665
The community have collaborating on 'the ultimate sharepoint development tool', not sure if you've seen this:
<a href="http://www.sharepointdevwiki.com/display/public/The+Ultimate+SharePoint+Development+Tool">http://www.sharepointdevwiki.com/display/public/The+Ultimate+SharePoint+Development+Tool</a>
The community have also put together a comparison on what development tools are out there with their pros and cons:
<a href="http://www.sharepointdevwiki.com/display/public/Solution+package+development+tool+comparisons">http://www.sharepointdevwiki.com/display/public/Solution+package+development+tool+comparisons</a>
There is discussion at the moment about fusing STSDev and WSPBuilder together, but it's early days...
Looking forward to see the next beta of VS2010 to have a play with this!
This is awesome news for those of us that develop heavily in SharePoint.
Doesn't microsoft pay you enough? Drop the ads on your blog. I understand ads on some housewife's blog where she's just trying to make ends meet, but ads on a high paid microsoft executive? Give me a break - the economy can't be that bad. It just smells of someone using their corporate position of authority for personal gain (outside of their normal salary).
Lose the ads.
@mesan
Ads? Where? I can't find any using IE or FF (all adblockers disabled).
Hi Mesan,
I have mentioned this a couple of times before. There is no personal gain here. Any and all proceeds from this go directly to a non-profit organization.
-somasegar
Finally some good tools for Office System developers,
next in line should be Dynamics CRM ....
Thank you Somasegar! I am very excited to see that the developer division at Microsoft is taking SharePoint under its wings. The web form designers and user controls are super critical. The ability to specify custom actions when the forms are submitted is also very important.
Please open the tools development and feature list to the public so the SharePoint team and you can get some much needed detail and feedback on what works and what needs tweaking.
This spans beyond office system in my opinion. SharePoint is not used as a starter kit for most blogs or wikis today because its just not entirely solid as an internet facing deployment. Hopefully this deep Visual Studio integration will foster some new innovation like people find in Moodle, Drupal, and other CMS / social Networking platforms.
The other major pitfall in my opinion is the web services API in SharePoint is very poorly documented and near impossible to code with. I hope we see a standard SOAP based API, with entity documentation, deployment tools, and solution accelerators like we see in Microsoft Dynamics CRM.
Soma posted on the new SharePoint and Visual Studio integration coming in the next release of Visual
Does it need to be installed on a system with Sharepoint to get it to work? Say for instance our development environment is Vista, can I use to develop and then deploy to W2K3 or W2K8?
Thanks.
Hi Kris,
Yes, Visual Studio and SharePoint need to be installed on the same machine for development. Currently SharePoint only supports installation on server operating system versions.
Una herramienta clave en el mundo del desarrollo para SharePoint son las extensiones de Visual Studio
This week we released an updated CTP of VSeWSS 1.3 here . Let us know your feedback on the Connect Site
http://blogs.msdn.com/somasegar/archive/2009/02/19/sharepoint-tools-support-in-visual-studio.aspx