Skip to main content

Windows Azure Tools for Visual Studio 2010 - August 2011 Upgrade

Last week the Windows Azure time did not only announced the availability of the Windows Azure Storage Analytics feature but also released Windows Azure Tools for Visual Studio 2010 - August 2011 Upgrade.

Some features that are included are:

  • Profiling the application running in Windows Azure.
  • New ASP.NET MVC 3 web role template.
  • Multi-configuration files in one cloud project.
  • More validation in the service package and deployment phase.
Download and Install

The easiest way to install the upgrade is by using the Web Platform Installer which can be found here. The WebPI will download some dependency packages besides, such as the latest Windows Azure SDK, ASP.NET MVC 3 for Windows Azure, etc.

ASP.NET MVC 3 Web Role

When creating a new cloud project you now have a  new ASP.NET MVC 3 Web Role template available. This template already added all the required  assemblies related to MVC3 and set the Copy Local = True by default.

Multiple Service Configurations

Under the cloud project we can find that there are two service configuration files (CSCFG) which are:

  • ServiceConfiguration.Cloud.cscfg
  • ServiceConfiguration.Local.cscfg

The Multiple Service Configurations feature makes it easier to switch between the local emulator and the real cloud environment. With two configuration files enabled, we can choose which one will be the service configuration file when locally debugging, packaging and deploying. 

New Package and Publish Window

Previously we choose to package or publish our windows azure project by selecting the radio button in the Publish window. In this upgrade the package and publish had been totally separated. In the context menu of the windows azure project we can create a package by using the Package menu, and use the Publish menu to deploy the application directly to the cloud.

More Validation

Because of the differences between the local emulator and the real cloud environment, deploying a Windows Azure project can be a trial-and-error process.  With the new tools update, Visual Studio helps us to validate our project and detect some common mistakes(like not setting Copy Local=True, connection to a local database, etc…).

Powered by ASP.NET Universal Providers

The ASP.NET Universal Providers extends the Session, Membership, Roles and Profile support to SQL Compact Edition and SQL Azure, which means as a developer, we can implement the business logic regardless which backend database we are using. More information in Scott’s blog post.

Go try it out yourself!

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more