How To: Upgrade Projects to the Current Version of the Windows Azure Tools

If a project is automatically upgraded or you specify that you want to upgrade it, your project is modified to work with current versions of certain assemblies, and some properties are also changed as this section describes. If your project requires other changes to be compatible with the newer version of the tools, you must make those changes manually.

• The web.config file for web roles and the app.config file for worker roles are updated to reference the newer version of Microsoft.WindowsAzure.Diagnostics.DiagnosticMonitoirTraceListener.dll.
  
  
• The Microsoft.WindowsAzure.StorageClient.dll, Microsoft.WindowsAzure.Diagnostics.dll, and Microsoft.WindowsAzure.ServiceRuntime.dll assemblies are upgraded to the new versions.
  
  
• Publish profiles that were stored in the Azure project file (.ccproj) are moved to a separate file, with the extension .azurePubXml, in the Publish subdirectory.
  
  
• Some properties in the publish profile are updated to support new and changed features. AllowUpgrade is replaced by DeploymentReplacementMethod because you can update a deployed cloud service simultaneously or incrementally.
  
  
• The property UseIISExpressByDefault is added and set to false so that the web server that’s used for debugging won’t automatically change from Internet Information Services (IIS) to IIS Express. IIS Express is the default web server for projects that are created with the newer releases of the tools.
  
  
• If Windows Azure Caching is hosted in one or more of your project’s roles, some properties in the service configuration (.cscfg file) and service definition (.csdef file) are changed when a project is upgraded. If the project uses the Windows Azure Caching NuGet package, the project is upgraded to the most recent version of the package. You should open the web.config file and verify that the client configuration was maintained properly during the upgrade process. If you added the references to Windows Azure Caching client assemblies without using the NuGet package, these assemblies won't be updated; you must manually update these references to the new versions. For more information about how to upgrade projects that use Windows Azure Caching, including instructions for verifying your web.config files, see How To: Upgrade and Verify Projects Using Windows Azure Caching
  
  

Warning
For F# projects, you must manually update references to Windows Azure assemblies so that they reference the newer versions of those assemblies.

How to upgrade a Windows Azure project to the current release

Concepts