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

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.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...