Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

Migrating SCSF 2008 Solutions to SCSF2010

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.
This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
To create client business applications using current Microsoft technologies, see patterns & practices' Prism.

This topic describes how to migrate existing smart client solutions (created with the Smart Client Software Factory – April 2008 release) to use the guidance package provided in SCSF2010.

To migrate existing smart client solutions to use the guidance package provided in SCSF2010:

  1. Open your solution using Visual Studio 2010.
  2. If your solution contains a Web Site and you get a warning message saying that a Web Site is targeting an older .Net Framework version, make sure the checkbox in the dialog is selected and click OK.
Ff699327.note(en-us,PandP.10).gifNote:
Framework manifest contains location for package SmartClientFactorypackage2008apr configuration file, but the file was not found. Do you want to permanently remove the package from the current solution?
Click on No and proceed to next step.

  1. Replace the following references with the SCSF assemblies to use SCSF 2010.
    • Microsoft.Practices.CompositeUI.dll
    • Microsoft.Practices.CompositeUI.Winforms.dll
    • Microsoft.Practices.CompositeUI.WPF.dll (if necessary)
    • Microsoft.Practices.SmartClient.ConnectionMonitor.dll (if necessary)
    • Microsoft.Practices.SmartClient.EndpointCatalog.dll (if necessary)
    • Microsoft.Practices.SmartClient.DisconnectedAgent.dll (if necessary)
    • Microsoft.Practices.SmartClient.EnterpriseLibrary.dll (if necessary)
  2. Replace the following references in your solution with the Enterprise Library 5.0 assemblies.
    • Microsoft.Practices.EnterpriseLibrary.Common.dll
    • Microsoft.Practices.EnterpriseLibrary.Data.dll
    • Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.dll
    • Microsoft.Practices.EnterpriseLibrary.ExceptionHandling.Logging.dll
    • Microsoft.Practices.EnterpriseLibrary.Logging.dll
    • Microsoft.Practices.ObjectBuilder.dll
  3. If your solution depends on a SQL Server Compact Edition DataBase:
    • Add a reference to the Microsoft.Practices.EnterpriseLibrary.Data.SqlCE.dll assembly.
    • In the app.config files of your application, update the provider name attribute to “System.Data.SqlServerCe.3.5” in all the connection strings for SQL Compact Edition 3.5.
    • In the same app.config files, update the name attribute of the provider mappings that use the connection strings modified in the previous step to “System.Data.SqlServerCe.3.5”.
  4. Add a reference to the following Service Location assembly in each project that has a reference to an Enterprise Library assembly.
    • Microsoft.Practices.ServiceLocation.dll
  5. Add a reference to the following Unity 2.0 assemblies in each project that has a reference to an Enterprise Library assembly.
    • Microsoft.Practices.Unity.dll
    • Microsoft.Practices.Unity.Interception.dll
  6. Update the Version and PublicKeyToken attributes of Enterprise Library assemblies in the app.config file of your application. For example, the following line:
    <section name="securityConfiguration" type="Microsoft.Practices.EnterpriseLibrary.Security.Configuration.SecuritySettings, Microsoft.Practices.EnterpriseLibrary.Security, Version=3.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
    


    Should be replaced with this one:

    <section name="securityConfiguration" type="Microsoft.Practices.EnterpriseLibrary.Security.Configuration.SecuritySettings, Microsoft.Practices.EnterpriseLibrary.Security, Version=5.0.414.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
    
  7. Update the Version and PublicKeyToken attributes of CompositeUI and CompositeUI.WinForms assemblies in the app.config file of your application. For example, the following line:
    <add type="Microsoft.Practices.CompositeUI.EventBroker.EventTopicException, Microsoft.Practices.CompositeUI, Version=1.0.51205.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" postHandlingAction="NotifyRethrow" name="EventTopicException">
    

    Should be replaced with this one:

    <add type="Microsoft.Practices.CompositeUI.EventBroker.EventTopicException, Microsoft.Practices.CompositeUI, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" postHandlingAction="NotifyRethrow" name="EventTopicException">
    

  8. On the Tools menu, click Guidance Package Manager. The Guidance Package Manager window will appear.
  9. Click Enable / Disable Packages.
  10. From the list of packages, select Smart Client Development – May 2010, and then click OK. The Guidance Package Manager will enable the guidance package.
  11. Click Close to close the Guidance Package Manager.


Show:
© 2015 Microsoft