Skip to main content

Web Deploy Improvements in ASP.NET and Web Tools 2012.2 Update

Last week Scott Guthrie announced the release of the ASP.NET and Web Tools 2012.2 Update. This release not only offers some really nice new features for ASP.NET WebForms, ASP.NET MVC, ASP.NET Web API, SignalR and the web tooling in Visual Studio, but also adds some nice improvements to Web Deploy. (For the full list of new features, have a look at the release notes). 

What’s new?
  • First of all, Web site projects now have the same publishing experience as Web Application projects including publishing to Windows Azure Web Sites. 
  • Selective publish – for one or more files you can perform the following actions (after publishing to a Web Deploy endpoint):
    • Publish selected files.
    • See the difference between a local file and a remote file. (this even works for images!)
    • Update the local file with the remote file or update the remote file with the local file.
  • Apply config transformations on the publish profile next to the build profile.
    • This will combine the transformations you’ve specified at the build profile level with the transformations you’ve specified at the publish profile level.
    • An example:
      • “You have a QA environment and want to apply the same transformation to both a release and debug build. Before you had to configure a build configuration for every combination. In this case it was QA-Release and QA-Debug and copy the same transformation over between the 2 configs. Now you can create a config transform for QA, and keep the Release and Debug build configuration intact.”
  • One that isn’t new, but I want to mention again is the web.config transform preview. This allows you to preview the result of a transformation.It was added when releasing VS 2012 but a lot of people don’t know it exists.

PreviewTransform

For more information, have a look at the videos from Sayed Ibrahim Hashimi.

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

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

The role of ActivitySource in OpenTelemetry for .NET

While doing some pair programming to integrate OpenTelemetry tracing to a .NET application, we had a discussion on how to use the ActivitySource . It looks simple. You new one up, give it a name, start an activity, done. The discussion started when we added a second ActivitySource with the exact same name in a different class. This made us wonder: "Are we duplicating traces now? Is this a memory leak? Do we need a singleton?" So we decided to dig deeper. This post is what we learned… What ActivitySource actually is ActivitySource is part of System.Diagnostics , not part of the OpenTelemetry NuGet packages. Microsoft built tracing primitives directly into the BCL, and OpenTelemetry's .NET SDK simply listens to them. This is why you can add distributed tracing to a library without taking a dependency on OpenTelemetry at all. An ActivitySource is a factory for Activity objects, and an Activity is .NET's name for what OpenTelemetry calls a span.(don’t ask m...
Read more