5. Microsoft Office SharePoint Server (MOSS) 2007 SDK Version 1.5 released April 2009 Updates Tools – Business Data Catalog Editor fixes Samples – New search federation samples Offline Searchable Help Updated
6. Download Link, Size and Details http://www.microsoft.com/downloads/en/details.aspx?FamilyId=6D94E307-67D9-41AC-B2D6-0074D6286FA9&displaylang=en
7. VSeWSS 1.3 March 2009 Visual Studio Extensions for Windows SharePoint Services is often abbreviated as VSeWSS (sounds like WYSIWIG) Item templates and project templates A comprehensive user guide is included.
8. Download Information Visual Studio 2008 extensions for Windows SharePoint Services 3.0, v1.3 - Mar 2009 CTP http://www.microsoft.com/downloads/en/details.aspx?FamilyID=FB9D4B85-DA2A-432E-91FB-D505199C49F6
22. Your Feedback is Important Please fill out a session evaluation form. Thank you! Tom Resing Resingnet-website@yahoo.com http://tomresing.com
Notes de l'éditeur
Here’s today’s agenda. I’ll tell you why I’m talking about this, then dig in to the 2007 tool updates and a demo of one. Then I’ll briefly cover what changed for developers in 2010 and compare the 2007 experience with a 2010 demo. And I’ll finish covering some migration techniques and demo one of them
Is the world you live in ever simple? We’ve had SharePoint 2010 released for 1 full year now. How many of you work exclusively in SharePoint 2020 today? For many of us, you’re living our dream. How easy would it be if we only ever had to work with one version of a product at a time? The reality for many of us is that we change jobs, we change projects and we change product versions or end up using both at the same time. If you only use 2010 today, you may yet find yourself upgrading from 2007 tomorrow. One example I see is when one company buys another and merges systems. And of course all those 2007 deployments that need to be upgraded.
The MOSS and WSS Software Development Kits have changed quite a lot over the years. Not only are there new samples and updated tools that work better than original versions, but the downloadable, offline searchable help files represent the latest guidance that will help you move forward towards 2010. You can see some examples of what was updated with the last release 2 years ago. I don’t expect any new updates, but I’ve found many developers I’ve talked to are unaware how much has changed over time in this very important download over the years.
This link will be available in the downloadable version of this slide so you don’t have to scramble to write it down now. Note that the SDK is a 197 megabyte download. It takes some room to hold everything SharePoint related from MSDN in the .chm help files.
Visual Studio Extensions for Windows SharePoint Services provide one great way to code and package SharePoint 2007 customizations. I’m going to quickly make a web part that shows a map from Bing in case you haven’t seen how easy that is in the 1.3 version update.
Note the Package, Deploy, Quick Deploy and Retract options VSeWSS adds
The build steps for the deploy option show that the solution is created, added, deployed and activated. Then the application pool is recycled which is necessary for GAC deployments.
When you develop for SharePoint 2010, Visual Studio 2010 is the tool of choice. In fact, 2010 versions of both products represent the first time the Visual Studio team dedicated specific effort towards providing tooling for SharePoint. And it’s good tooling.
I’m going to step through an example of creating a customization with the new SharePoint tools that shipped with Visual Studio 2010. You’ll see that the experience on the surface is actually fairly similar to the extensions built for SharePoint 2007, but don’t be fooled. In 2010, it goes much further and the extensibility options for developers to add on to these tools are very rich, as well.