Azure SDK for .NET 2.3 Release Notes
Updated: July 1, 2015
The Azure SDK for .NET version number (2.3) is determined by the core Azure service runtime assembly using semantic versioning. Other client libraries packaged inside the Azure SDK for .NET, along with their respective NuGet packages, follow independent versioning based on the semantic versioning scheme.
The Azure SDK for .NET 2.3 includes Azure Storage 3.0, Azure Service Bus 2.2.7, Azure Caching 1.7.0, and Azure Configuration Manager 2.0.3 libraries. You can also download these libraries from their respective NuGet packages.
For more information related to this release, see the following resources:
New features in the Azure Tools for Microsoft Visual Studio - What's New in the Azure Tools
New features and release notes for Azure Service Bus - Release Notes for Service Bus
New features and release notes for the Azure Plugin for Eclipse with Java (by Microsoft Open Technologies) - What's New in the Azure Plugin for Eclipse with Java (by Microsoft Open Technologies)
The following are new features and updates in the Azure SDK for .NET 2.3:
Updated File…New ASP.NET wizard (Visual Studio 2013)- Easily provision and create Websites or Virtual Machines in Azure, as well as PowerShell publishing scripts.
Updated Publish Web wizard (Visual Studio 2012 and 2013)- The Publish Web wizard is simpler to use and now you can publish to Virtual Machines. You can also use generated PowerShell scripts to quickly deploy Azure Websites and virtual machines.
Server Explorer (Visual Studio 2012 and 2013)- Use new features in Server Explorer to create Virtual Machines, send messages for Notification Hubs, and view Website tracing and data logs for easier troubleshooting. The Websites node also enables you to remotely view and edit files from your site, useful for turning custom errors on/off.
Diagnostics and debugging (Visual Studio 2012 and 2013)- Remotely diagnose application issues using new remote debugging for Virtual Machines and new native code debugging. Debug Cloud Services locally with Emulator Express, which is now GA and the default option for new Cloud Service projects. Improvements have also been made to the Storage Emulator.
PowerShell- Visual Studio now supports colorization of PowerShell files when PowerShell 3.0 or higher is installed.
Service Bus-Auto forwarding, message receive semantics for sessions, client side batching when sending messages, and other new features have been added to Service Bus. For more information, see What's New in the Azure SDK 2.3 Release (April 2014).
New APIs and PowerShell modules- Try out these new APIs and PowerShell modules:
Try out the RC features available in Visual Studio 2013 Update 2 RC:
Mobile development- Leverage your .NET skills to create and deploy .NET Mobile Services for Windows Store, Windows Phone, iOS, and Android apps directly from Visual Studio. Diagnose application issues using the new capability for remote debugging .NET Mobile Services.
JSON editing- The JSON editor now includes colorization, parsing, validation, and schema-driven IntelliSense.
Browse/debug an SSL enabled IIS Express website- A new dialog installs a certificate for IIS Express that allows browsing/debugging an SSL enabled IIS Express website without warnings.
The following are known issues in the Azure SDK for .NET 2.3:
MVC4 Web Role will not be available when creating a new cloud service project after installing Visual Studio Update 2 RC- After installing Visual Studio Update 2 RC, MVC4 Web Role will not be available in the New Windows Azure Cloud Service dialog when creating a new cloud service project with.NET Framework set to 4.0.
To resolve this issue, you must revert to Visual Studio RTM by uninstalling Visual Studio Update 2 from Installed Updates in Add/Remove Programs.
Warnings when building a Cloud Services project with a WebRole in Visual Studio 2013 RTM – Visual Studio 2013 RTM and Azure SDK 2.3 do not add the correct binding redirects for the Microsoft.Data.OData library. Building a Cloud Services project will generate warnings similar to the following:
Warning 1 Found conflicts between different versions of the same dependent assembly. In Visual Studio, double-click this warning (or select it and press Enter) to fix the conflicts; otherwise, add the following binding redirects to the "runtime" node in the application configuration file: …
Starting Emulator Express with port override in non-administrator mode fails- The port will not be auto-adjusted by Emulator Express if the overridden port is less than 8080. Emulator Express will fail to start and you’ll see an error message similar to the following:
Cannot override to port 2051. New port below minimum allowed value 8080 for protocol http.
To work around this issue, start the Emulator Express without port override when running in non-administrator mode. Or, change the port to a value greater than 8080. To change the port value, right-click on the web role project in Solution Explorer and select Properties. On the Web tab change the Project URL port to a number greater than 8080, then build and debug the project.
Azure SDK 2.3 install failure corrupts Visual Studio 2013 installation- If you install the Azure SDK 2.3 with Visual Studio 2013 and the installation fails, you must repair Visual Studio and re-install the Azure SDK.
CSRun requires an elevated command prompt – Tools and scripts that use the CSRun command-line tool (csrun.exe) to launch the compute emulator, including Azure PowerShell, should be run from an elevated command prompt, or you may receive an error like the following: “The compute emulator has an error: Compute Emulator needs to be launched with administrator privileges in order to run in full emulation mode. Please restart the emulator with correct privileges.”
Edit and Continue
In a 64-bit environment, Edit and Continue requires Visual Studio 2013 and .NET Framework 4.5.1 (since .NET Framework 4.5.1 is always installed with Visual Studio 2013 and it is an in-place upgrade of .NET Framework 4.5, Edit and Continue will still work in Visual Studio 2013 even when targeting .NET Framework 4.5 on x64 machines).
In a 32-bit environment, Edit and Continue works in both Visual Studio 2012 and Visual Studio 2013.
Edit and Continue requires Azure projects to target IIS Express when F5, it doesn’t work with full IIS. Expect to see “Edit and Continue not allowed” dialog.
Edit and Continue doesn’t work in the WebRole.OnStart event. Expect to see “Edit and Continue not allowed” dialog.
Edit and Continue works with both full emulator and express emulator.
When targeting full emulator, Edit and Continue will only apply changes to the one instance that causes the break (breakpoint or exception), if a role has multiple instances, the behavior might be inconsistent after using Edit and Continue to apply changes to code on the fly.
The following are breaking changes in the Azure SDK for .NET 2.3:
The CSUpload command line tool is deprecated- In order to provide a consistent experience across all Azure management tools, CSUpload has been deprecated in Azure SDK2.3 and is no longer supported. To continue using tools supported by the platform, we recommend you switch to Azure Powershell Cmdlets. All CSUpload actions are supported through Powershell Cmdlets (exact cmdlet details can be found in the table below):