Just Published: Development Tools and Techniques for Working with Code in Windows SharePoint Services 3.0 (Parts 1 and 2)
I'm posting this on behalf of my colleague, Mike Fitzmaurice. In Mike's own words:
Have you wanted information on how to package web parts, event receivers, or list/feature/site definitions into solutions? How to deploy those solutions from a development environment to a test environment and then to production? How the deployment of application components and assets is different from content deployment? How to push a new version of a web part, feature, or application page out to a site that has the old version already in production?
This white paper covers it. So, go get it now!
I’m not saying that everything just became easy (it hasn’t), but I *am* saying that everything just became explicit. The paper has recommended practices, examples, etc. Although you still can’t upgrade a list/feature/site definition over an old one, this paper will show you how to deprecate the old one and have the new one take over for any newly-created sites/features/lists.
It also applies to MOSS 2007 just as much as WSS 3.0, but it’s all about platform issues, so it’s focused on the WSS base platform, and its title reflects that.
This white paper was written by Patrick Tisseghem of U2U and a SharePoint MVP, with heavy consultation from Mike Ammerlaan and myself. It’s what we recommend you do with the code and definitions you write.
<Lawrence />
