Upgrade custom Web Part packages (Windows SharePoint Services)
Updated: December 1, 2006
Applies To: Windows SharePoint Services 3.0
Topic Last Modified: 2007-12-13
Most custom Web Parts will continue working after upgrade. However, you should test your Web Parts in ASP.NET 2.0 to verify that they will work in the new environment. In particular, you must rebuild or redeploy custom Web Parts if you:
Used the ASP.NET 1.1 obfuscation tools. If you used these tools, you must rebuild your Web Parts by using ASP.NET 2.0.
Are moving to a new server farm by using the database migration path for upgrade. If you choose this upgrade path, you must redeploy your Web Parts to the new farm.
Have stored your custom Web Parts in the \BIN folder and are not upgrading in-place. Gradual upgrade does not upgrade items to the new \BIN folder, so you must redeploy your Web Parts.
To upgrade your Web Parts, test them in ASP.NET 2.0, and then either rebuild or redeploy any Web Parts that meet the criteria above.
This topic is included in the following downloadable book for easier reading and printing:
See the full list of available books at Downloadable books for Windows SharePoint Services.