Upgrading from Previous Releases
| Retired Content |
|---|
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. |
As mentioned in the previous topic, New in This Release, there are changes in the application blocks that will require changes to solutions created with previous releases of the application blocks.
Upgrading Solutions Developed with the Composite Web Client Library Bundle (Version 2007.11.16.5 or Earlier)
The following table lists the suggested changes to upgrade an existing solution created with the application blocks included in the Composite Web Client Library bundle (version 2007.11.16.5 or earlier).
| Compatibility issue | Suggested change |
|---|---|
| Solution needs to reference the new application blocks. | Delete all references to Microsoft.Practices.CompositeWeb and Microsoft.Practices.CompositeWeb.EnterpriseLibrary. Then add the references to Runtime Version v2.0.50727 / Version 2.0.2.0, which includes Microsoft.Practices.CompositeWeb and Microsoft.Practices.CompositeWeb.EnterpriseLibrary. If you are upgrading a Web site project, use the Property Pages dialog box to do this. |
Upgrading Solutions Developed with the Web Client Software Factory June 2007
The following table lists the suggested changes to upgrade an existing Web Client Software Factory June 2007 solution to make it work with the new application blocks.
| Compatibility issue | Suggested change |
|---|---|
| Solution needs to reference the new application blocks. Microsoft.Practices.ObjectBuilder.WCSFExtensions is merged into Microsoft.Practices.CompositeWeb.ObjectBuilder. | Delete all references to Microsoft.Practices.CompositeWeb, Microsoft.Practices.ObjectBuilder.WCSFExtensions, Microsoft.Practices.CompositeWeb.EnterpriseLibrary. Then add the references to Runtime Version v2.0.50727 / Version 2.0.2.0, which includes Microsoft.Practices.CompositeWeb and Microsoft.Practices.CompositeWeb.EnterpriseLibrary. If you are upgrading a Web site project, use the Property Pages dialog box to do this. |
| Dependency injection needs to be called explicitly for MasterPages, pages, and user controls to work correctly. This change will show up at run time. | A MasterPage should derive from Microsoft.Practices.CompositeWeb.Web.UI.MasterPage instead of System.Web.UI.MasterPage.A page should derive from Microsoft.Practices.CompositeWeb.Web.UI.Page instead of System.Web.UI.Page.A user control should derive from Microsoft.Practices.CompositeWeb.Web.UI.UserControl instead of System.Web.UI.UserControl. |
| ModuleInitializer's load method signature requires the use of the concrete class instead of the ICompositionContainer. This change will be detected at compile time. | In the ModuleInitializer load method, use the concrete class CompositionContainer instead of ICompositionContainer. |
| Microsoft.Practices.ObjectBuilder.WCSFExtensions is merged into Microsoft.Practices.CompositeWeb.ObjectBuilder. This change appears at compile time. | Change using statements from Using Microsoft.Practices.ObjectBuilder.WCSFExtensions; to Using Microsoft.Practices.CompositeWeb.ObjectBuilder;. |
| ServiceException and ModuleDependencySolverException no longer extend ApplicationException. They now extend Exception. | Check your code for places you are catching ApplicationException and see if you need to change it to catch specific exception types instead. |
| RootContainer is no longer accessible through Application[ApplicationConstants.RootContainer] state value. This is now only accessible through the WebClientApplication.RootContainer property. | Replace Application[ApplicationConstants.RootContainer] with WebClientApplication.RootContainer everywhere Application[ApplicationConstants.RootContainer] is used. |
Enabling October 2007 (Bundle) Solutions
This topic describes how to enable existing Web client solutions that were created with the Web Client Software Factory bundles to use the guidance package and block assemblies provided in the February 2008 release.
To use the latest Composite Web Application Block
- Copy the following assemblies from the Microsoft Practices Library folder in the Web Client Software Factory installation directory to the Library folder of your solution:
- Microsoft.Practices.CompositeWeb.dll
- Microsoft.Practices.CompositeWeb.EnterpriseLibrary.dll
- Microsoft.Practices.Web.UI.WebControls.dll
- Rebuild the solution.
To enable the February 2008 guidance package
- Open the solution in Visual Studio. If you have the October 2007 guidance package enabled in the solution, a dialog box appears that asks if you want to remove it. Click Yes.
- On the Tools menu, click Guidance Package Manager. The Guidance Package Manager window appears.
- Click Enable/Disable Packages.
- From the list of packages, select Web Client Development February 2008.
- Click OK. The Guidance Package Manager will enable the guidance package.
- Click Close to close the Guidance Package Manager.
