On SharePoint conference Steve Ballmer announced that SharePoint 2010 Beta2 is going to be released in November.
In one of the previous posts I mentioned all project and project item templates that are supported if you are developing against SharePoint 2010. To develop and use new project templates you will need a 64-bit client or server OS and 64-bit installation of SharePoint 2010.
Experience for developing for previous release of SharePoint (Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3) with Visual Studio 2010 has not changed compared to Visual Studio 2008.
See the below table for comparison between Visual Studio 2008 and Visual Studio 2010.
Visual Studio 2008
Visual Studio 2010
Sequential workflow and State Machine workflow
Sequential workflow and State Machine workflow (same project templates as in Visual Studio 2008)
All new features, project and project item templates (see previous post)
32-bit server OS and 32-bit MOSS only
32-bit server OS and 32-bit MOSS and WSS*
64-bit server or 64-bit client OS and 64-bit SharePoint 2010*
*64-bit OS and SharePoint are not supported
*Only 64-bit OS and SharePoint are supported
Check this link for hardware and software requirements for SharePoint Server 2010.
Windows 7 was released today and it was announced on SharePoint blog that Office and SharePoint Server 2010 will be available for broad Beta in November.
There is a good news for SharePoint developers – you can install SharePoint 2010 on both Windows 7 and Vista client machines. This means that you no longer need a server OS to develop for SharePoint (SharePoint 2010 client install is not supported for production only for development).
You can already get your Windows 7 copy online at Microsoft Store.
As you probably know, Visual Studio 2010 was announced earlier this week and it contains a lot of cool features and project templates for SharePoint developers. Below is a short overview for some of the SharePoint development related features and project templates.
With all new SharePoint project templates you can leverage new configurable deployment feature which lets you configure the way you want to deploy or retract your project. Besides using provided, out of the box deployment steps (Run Pre-Deployment Command, Run Post-Deployment Command, Recycle IIS Application Pool, Retract Solution, Add Solution, and Activate Features) you can use SharePoint extensibility to create your own, custom deployment steps and deployment configurations.
Some SharePoint projects can be deployed either as sandboxed or farm solutions. Sandboxed solutions run in a secure and monitored process that has limited resource access and with farm solutions user must have SharePoint administrator privileges to run or deploy the solution. You can read more about SharePoint sandboxed solution here.
Even though Visual Studio 2010 contains a set of project templates you can also extend them. You can create extensions for projects, project items, define your own project item types and create deployment extensions. You can read more about extending SharePoint tools on MSDN.
Feature and package designers give you the ability to customize features in your solution and with packaging designer you can customize which features are getting deployed and how. More about feature and package designer is here.
SharePoint Explorer is a new tool window that gives you a view into your SharePoint server. You can get a hierarchical view of lists, sites and workflows on your SharePoint server.
The following SharePoint specific project templates and project item templates are available in Visual Studio 2010:
Besides above mentioned project templates, there are two import project templates for importing .WSP file contents and importing reusable workflows:
If you are a MSDN subscriber, you can download Visual Studio 2010 from here. Download will be available to everyone on October 21st.
If you want to know how to download and install Visual Studio 2010 watch Channel9 video.
To get you started, head over to MSDN and read some of the walkthroughs on SharePoint Development in Visual Studio 2010.