The official source of product insight from the Visual Studio Engineering Team
Yesterday we announced the release of the Windows Azure SDK version 2.2 for Visual Studio 2012 and 2013. This release includes several new highly requested customer features like Integrated Sign In, Remote Debugging preview, Edit and Continue for Cloud Services, SQL Databases in Server Explorer, and Publishing Cloud Services to Affinity Groups. In addition with VS2013, we’ve also included Logs for Windows Azure Mobile Services. In this blog post, we’ll share more details on these new exciting features.
We’ve integrated the Sign In experience directly in Visual Studio so you can Sign In to Windows Azure with your Microsoft account or Organizational account without ever leaving the IDE. No need to create, download or distribute management certificates. This streamlines the experience for new customers and makes it easier for existing customers to access their Windows Azure services.
With the new Remote Debugging, you can attach the debugger to a running instance of a Windows Azure cloud service right from Visual Studio. Having the ability to debug a live cloud service is invaluable when trying to track down the pesky issues that only occur in a live running instance.
In addition to the remote debugger, we’ve also added support for Edit and Continue. You can now make changes to code during your debug session and see the impact of those changes without ever having to restart the session.
The SQL Database node is a welcomed addition to the Windows Azure Server Explorer. Now you can browse your SQL Azure databases without knowing the virtual machine or connection string to the database. We automatically configure the firewall so that you can access the database from your developer workstation. You can also open your SQL Azure database in SQL Object Explorer for a complete database management experience.
With this release, Cloud Services supports publishing to an Affinity Group rather than just a specific region. This allows you to group dependent services and deploy them in close proximity to one another to help improve performance and reduce network bandwidth.
In Server Explorer, with Visual Studio 2013, we’ve also added the ability to view your Mobile Service logs. You can make your table script changes and immediately view your logs all from within Visual Studio.
As always, the new SDK works side by side with the past two release of the Windows Azure SDK (versions 2.0 and 2.1) on both Visual Studio 2012 and 2013.
You can find additional details about what’s new in Windows Azure SDK 2.2 from Scott Guthrie’s blog post.
We’d love to hear back from you. You can comment on this post, use the send-a-smile feature from Visual Studio, submit bugs through Microsoft Connect, or post suggestions on Visual Studio User Voice.
Azure Tools Team
I've got VS2013, and have connected to Azure and can successfully deploy a site.
However, when I try to attach the debugger, it thinks for a while and then pops up a challenge box asking me for credentials. What credentials are these? I've tried the obvious permutations and none seem to work. I'm not even clear why I am being challenged, given that I have successfully logged in.
@Kaz, are you using Cloud Services or Web Sites?
I am using VS 2013 and Azure SDK 2.2.
So I have been doing right-click on the Azure project and select "Package" or "Publish" and then upload to the cloud.
All of sudden it stopped working. When I click "Publish" menu item I get "Object reference not found" exception. I tried uninstalling Azure SDK and reinstall, no use. How do I get it work again?