Skip to main content

Microsoft Web Essentials: a must have Visual Studio Extension for every web developer

With the release of Visual Studio 2012, Microsoft also updated some of their Visual Studio extensions. One of the extensions I like a lot are the Web Essentials tools and although the live of a web developer becomes a lot easier in Visual Studio 2012, there are still some missing features. Web Essentials 2012 tries to fill this gap.

So what’s new in this version?

  • Option dialog: Now it becomes possible to set the most important options through this dialog.
  • JSHint for JavaScript: JSHint is a really good way of making sure your JavaScript follows certain coding guidelines and best practices.
  • Better LESS and CoffeeScript: The LESS editor has been updated to truly take advantage of LESS. This includes:
    • Support for @import directives
    • Intellisense across imported .less files for Mixins and variables
    • All the validation from the CSS editor now shows up in LESS
    • Both CoffeeScript and LESS now uses the official compilers
    • Compiles and creates a .css/.js file when a LESS/CoffeeScript file is saved in VS
  • JavaScript regions: I’m not big fan of regions, but if you are a believer; Javascript regions is now also a part of the 2012 version
  • Re-embed base64 dataURIs:  allows you to keep your base64 dataURI’s up-to-date with the original image file as it changes.
  • Vendor help for @-directives: Vendor specific validation and Smart Tags are now also available for @-directives.
  • New performance validation: Three new validators have been added that analyses the CSS for general performance issues. They validation the following:
    • Small images should be inlined (base64 embedded)
    • Don’t use the universal selector (the star)
    • Don’t over qualify ID selectors

Of course the list of new features, bug fixes,… is a lot longer, have a look at Mads Kristensen blog for all the info.

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         ...

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) ...

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.