SharePoint 2010 DevelopmentRandall Isenhour
Hello SharePoint Developers!
We are excited to announce the availability of the latest updates to the online MSDN Library + the downloadable SDKs for both MOSS 2007 and WSS 3.0!
In our never-ending efforts to improve the customer and partner experience, we are announcing the sim ship of both the online MSDN Library and the downloadable SDK! No more confusion about what’s the latest version: August is August!
> Download the MOSS SDK 1.4 <
> Download the WSS SDK 1.4 <
The August 2008 update is version 1.4 and reflects feature enhancements that were part of the recent Infrastructure Update. For more information on SharePoint Products and Technologies updates, you can start here on TechNet.
If you are only writing code that utilizes the Windows SharePoint Services platform, you can download the WSS SDK. However, if you want the superset of all documentation and samples, you should install the MOSS SDK, and then you’ll get all the platform and technology information as well. You don’t need to download both, but you will need to uninstall all previous versions.
Note The SDK 1.4 downloads are full releases that include all previous tools and documentation.
The SDK updates in 1.4 include:
· Updated documentation files, including updated, offline versions of MSDN Library Technical Articles and Developer Guides What’s New in the MOSS SDK 1.4 DocumentationWhat’s New in the WSS SDK 1.4 Documentation
· Lots of new documentation for Records Management APIs.
You can also update the Visual Studio Extensions for SharePoint Services. Here is the link to the installer: VSeWSS 1.2. The extensions were updated on 7/1/2008 and now work with Visual Studio 2008!
Don’t forget to download the user’s guide: version 1.1
We want to make sure you have all the information you expect to find in the SDK. Please reply to this blog entry with comments if you have a request. And don't forget to use the Community Content Wiki on MSDN to annotate the SDK documentation online with your own insights. Just look toward the bottom of each page online or click the Add Content... button in the top-level menu on MSDN Library pages.
I had a question today about SharePoint Workflow "Dos and Don'ts" and I thought it might be a good idea to share the response more broadly.
I'm also working on compiling a list of Best Practices for Custom Application Development in SharePoint, which will be published next month on MSDN as part of a larger MSDN/TechNet series on the subject of guidance and best practices. Stay tuned for updates...
SharePoint Workflow Resources
The Workflow Resource Center on MSDN is a good place to start for guidance: http://msdn.microsoft.com/en-us/office/bb421687.aspx.
**Update 8/29: Here is a great Workflow Best Practices paper as well: Developing Workflow Solutions with SharePoint Server 2007 and Windows Workflow Foundation
Developing Workflow Solutions with SharePoint Server 2007 and Windows Workflow Foundation
This blogger also did a good job compiling links within the SDK and to other MSDN & Web resources, as well as other sources of Best Practices for Workflows:
Also, the downloadable MOSS SDK has a lot of workflow templates and samples.
Knowing when to use SharePoint Designer (SPD) workflows v. Visual Studio (VS) workflows
A good place to start is with the freshly updated SDK: http://msdn.microsoft.com/en-us/library/ms461944.aspx.
There is also this guidance offered in the SharePoint team blog:
SPD is geared toward the Web Designer/Business admin. It's easy to learn, and you don't have to write any code. You can put together a lot of workflows with just sequence of actions and conditions. The other cool thing about SPD is that you can deploy remotely (vs. VS, where you have to deploy on the server box)
However, there are a few limitations (deploys to one list at a time, no InfoPath forms, only sequential workflows). So you will want to use VS if…
· You need to create a workflow that can be deployed to all lists in a site collection.
· You want to use InfoPath forms for your workflow
· You need more actions than the ones available by default in SPD
· You want to use state machine workflows
Hope this helps,