Your extension will be available shortly on the Visual Studio Marketplace at this link.

Web Essentials 2012

Free

Adds many useful features to Visual Studio for web developers.

(197)
Visual Studio
2012
Download (1,149,333)
6/1/2015
3.8
View
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Description
Sign in to write a review
Sort by:

by VB6 Programming | July 31 2016

Better than 2015 Web Essentials

by coderbd | July 28 2016

As a front end developer. I'm very much exited about minification process of this.

by Jony Green | September 06 2015

I'm not a developer, i always use free online js minifier(http://www.online-code.net/minify-js.html) and css compressor(http://www.online-code.net/minify-css.html).

by Dan Randolph | May 01 2015

I love the css help.

by Ammar.Zaied | February 13 2015

nice !

by Gene Kohli | January 21 2015

Sweet Suite!

by Bob Blork | May 30 2014

nice!

by Shreeharsh Ambli | April 17 2014

brings in new capabilities

by Ilya Galakhov | February 19 2014

Thank You!

by Jitbit1 | February 04 2014

No more LESS support in the latest version. But "LESS" is there on the product page, there's even a LESS-settings tab in the options. Thanks for ruining our work process.

This extension is #1 result in Google for "Visual Studio LESS".

PS. the new "ASP.NET and Web Tools 2012.2" only highlights LESS code, but does not compile it!! So your answer does not help!!

by Proco | January 27 2014

Amazing extension!

by Richard D | December 19 2013

Nice tools, but unfortunately Typescript is left out of the recent update. So a lot of the functionality I used is not available anymore.

:-(

by harwi | Sat 4:39 PM

Great tool!

by Breno Queiroz | November 27 2013

You Must Have It!

by Balaji M Kundalam | November 23 2013

Useful add on.

by GK Dev | November 20 2013

by TW Scannell | November 19 2013

This says is updated today.It fails to install in VS 2012 Express

Mads Kristensen November 20 2013
| Edit |
Delete

Unfortunately, VS Express doesn't support 3rd party extension. It's not a limitation of Web Essentials

by Eliezer Perlmutter | November 01 2013

by Leonardo Lourenço Silva | November 01 2013

Very USeful !!!

by Christiaan Rakowski | October 28 2013

1 - 20 of 196 Items   
Sign in to start a discussion


  • How to install 2.9?
    2 Posts | Last post August 29, 2013
    • 3.0 removed TypeScript support I relay on, is there any way to install 2.9 back?
    • Hello, you could get it here: http://vswebessentials.com/nightly/webessentials2012-2.9.vsix
      
      In fact I think that removing TypeScript is very sad because Web Essentials was supporting TypeScript much better than original TypeScript extension. I spent few days trying to adapt to extension from TypeScript team and I've realized that theirs "Compile-on-save" and "Compile-on-build" features are verry buggy.
  • JSHint custom Environment variables
    2 Posts | Last post August 28, 2013
    • Is it possible to somehow set custom Environment variables for JSHint such as Ember?
      And if so, it would be brilliant if that could be added to the interface in options
    • I also have the need for adding Custom Environment variables.  For now I have to add a /*global...*/ to every file but this is annoying because I can't just copy and paste it.  If any of those variables aren't used It shows a warning.  I know I could turn that check off but I like it on for the rest of my code and it really shouldn't check the /*global for variables names.  If I could add a Custom Environment that would solve this problem.
  • Why amd configuration missing in v2.9?
    24 Posts | Last post August 28, 2013
    • Why amd configuration missing in v2.9?
    • I 2nd that. The amd compiler switch is missing from the Settings dialog in 2.9 (VS2012)
      
    • The default setting is true? I get the setting in the file "%users%\Web Essentials\WE-settings.xml"
    • Yeah, the TypeScriptUseAmdModule node is set to true in my we-settings.xml file but the compiler is still compiling to CommonJS so something is still going kaput somewhere
    • Balmers got to go.
    • No, in all seriousness. Irritated by having spent the whole morning trying to understand why my project suddenly stopped working after this update. Now I've set up the nightly build extension to see it's Version 2.5.6.2, but you've released 2.9? But at least the AMD option is there. Sorry to moan. 
    • Very irritated by this too. Wasted morning thanks to this.
    • Anyone have the link to previous version 2.8? 
    • Same issue. Very annoying. How do I fix this or get around it?
    • OK, so I guess that the solution is to use the nightly build for now, although it looks like it is actually an older version.
      
      Please fix this in the latest version, since Web Essentials is VERY ESSENTIAL for Typescript development.
    • It looks like version 2.6 is available from http://vswebessentials.com/nightly/webessentials2012-2.6.vsix - that is at least a little newer than 2.5.6.2 that is available through the not-so-nightly builds channel.
    • @Egil, thanks for the link. Looks like 2.7 is also available.
      
      http://vswebessentials.com/nightly/webessentials2012-2.7.vsix
    • Yeah great thank for link 2.7 !
      
      It's working back. Hope that web essentials will fix this bug.
    • +1 to Calvin Willman's fake troll comment "Ballmers got to go." Got a good laugh. :-)
    • Mads stated on Git Hub that the TypeScript team is changing the compiler's support for AMD.
      
      https://github.com/madskristensen/WebEssentials2013/issues/41
      
      I speculate that they will provide some sort of AMD directive that you can include in your TS file.  This way you can control how each file gets compiled rather than specifying it globally with in Web Essentials or at a solution or project level.
      
      Currently they support the //AMD-Dependency directive, so this would just be an extension of this concept. 
      
      This would also explain why it was intentionally removed in this release.
    • @Khoi_Pham, can you explain how to use the //AMD-Dependency directive?
    • @egil the exact syntax is:
      
      ///<amd-dependency path="bootstrap" />
      
      This forces the compiler to include the dependency in the define statement in final javascript. It gets added at the end.  
      
      see this example:
      
      http://www.typescriptlang.org/Playground/#src=%2F%2F%2F%3Camd-dependency%20path%3D%22bootstrap%22%2F%3E%0Adeclare%20module%20%22foo%22%7B%0A%09export%20var%20greeting%3Astring%0A%7D%0Aimport%20foo%20%3D%20require(%22foo%22)%3B%0Aalert(foo.greeting)%3B
      
      This is useful when you reference definition files that don't declare a file module but want to output the dependency in the final javascript.  Think Jquery plugins
    • @Khoi_Pham Awesome, thanks. I wonder if this could be used to include dependencies on typescript modules as well, i.e. force the compiler into AMD mode.
    • In the TypeScript 0.9.1 compiler (released about 3 days ago), the --module AMD flag must still be used when compiling AMD modules.
      
      Our quite large codebase entirely relies on compiling with this flag, and the ///<amd-dependency/> reference cannot replace this.
      
      The statement from Mads C about why the option was removed from Web Essentials settings seems to be that the TypeScript team are working on some changes around AMD modules.
      
      But why the h was this option removed from the Web Essentials settings before there is an alternative?
      
      We basically cannot use Web Essentials 2.9, and told everyone in the team to stay away from it. Please revert this meaningless change.
    • Anyone have the link to the Web Essentials 2012 2.9 open source project? I'd like to take a look and add back in the AMD flag.
      
      I can only find the git hub link for 2013.
    • I fail to understand the current situation. Probably I missed some important information somewhere. I know...
      
      Since WE 2.9 the option for "TypeScript AMD module" does not exist any longer. Version WE 2.8 and WE 2.8.1 had that option, but they are not available for download. The Nightly Build offers version 2.5.6.2. The download page offers WE 2.6.
      
      So what should I do after having installed and then de-installed WE 2.9? How can I bring back the AMD option? Should I go back to WE 2.6?
    • https://github.com/madskristensen/WebEssentials2013/issues/41
      this solves it, at least for now.
    • It would be a good idea, if version 2.8.1 were offered for download. As far as I know that is the last version that supported the AMD options. It would help those developers who updated from 2.8.1 to 2.9.
    • Seems this is the definitive answer why it's being phased out of WE. http://madskristensen.net/post/Web-Essentials-2013-Where-is-the-TypeScript-support.aspx
  • Errors on build
    3 Posts | Last post August 27, 2013
    • Building our MVC Web app displays:
      
      8/5/2013 8:32:00 AM: The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG))
         at EnvDTE.Properties.Item(Object index)
         at MadsKristensen.EditorExtensions.ProjectHelpers.GetRootFolder()
         at EnvDTE.Properties.Item(Object index)
         at MadsKristensen.EditorExtensions.ProjectHelpers.GetRootFolder()
      
      in the output under Web Essentials.
      
      I actually have all the compilers (LESS, TypeScript, JSHint CoffeeScript) turned off.
      
    • I just upgraded to V3 of Web Essentials 2012 and also got the same error after building our WPF application:
      
      ========== Build: 95 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
      26/08/2013 2:17:54 PM: The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG))
         at EnvDTE.Properties.Item(Object index)
         at MadsKristensen.EditorExtensions.ProjectHelpers.GetRootFolder()
         at EnvDTE.Properties.Item(Object index)
         at MadsKristensen.EditorExtensions.ProjectHelpers.GetRootFolder()
      26/08/2013 2:17:54 PM: The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG))
         at EnvDTE.Properties.Item(Object index)
         at MadsKristensen.EditorExtensions.ProjectHelpers.GetRootFolder()
         at EnvDTE.Properties.Item(Object index)
         at MadsKristensen.EditorExtensions.ProjectHelpers.GetRootFolder()
      26/08/2013 2:17:54 PM: The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG))
         at EnvDTE.Properties.Item(Object index)
         at MadsKristensen.EditorExtensions.ProjectHelpers.GetRootFolder()
         at EnvDTE.Properties.Item(Object index)
         at MadsKristensen.EditorExtensions.ProjectHelpers.GetRootFolder()
      26/08/2013 2:17:54 PM: The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG))
         at EnvDTE.Properties.Item(Object index)
         at MadsKristensen.EditorExtensions.ProjectHelpers.GetRootFolder()
         at EnvDTE.Properties.Item(Object index)
         at MadsKristensen.EditorExtensions.ProjectHelpers.GetRootFolder()
      26/08/2013 2:17:54 PM: The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG))
         at EnvDTE.Properties.Item(Object index)
         at MadsKristensen.EditorExtensions.ProjectHelpers.GetRootFolder()
         at EnvDTE.Properties.Item(Object index)
         at MadsKristensen.EditorExtensions.ProjectHelpers.GetRootFolder()
      26/08/2013 2:17:54 PM: The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG))
         at EnvDTE.Properties.Item(Object index)
         at MadsKristensen.EditorExt
    • I just updated today (8/27/2013) to version 3.0 and I am now getting the same HRESULT: 0x80070057 (E_INVALIDARG) error in my build output. It is not preventing my solution from building though, thankfully.
  • v3 on Build get error "The Parameter is incorrect Exception from HRESULT:0x80070057 (E_INVALIDARG))
    2 Posts | Last post August 26, 2013
    • Just updated to v3 (2012) and receive this build log on build  (VS 2012 Update 2)
      
      The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG))
         at EnvDTE.Properties.Item(Object index)
         at MadsKristensen.EditorExtensions.ProjectHelpers.GetRootFolder()
         at EnvDTE.Properties.Item(Object index)
         at MadsKristensen.EditorExtensions.ProjectHelpers.GetRootFolder()
    • Sorry didn't realise it was alreayd reported by @jtsom
  • LESS calc() compilation bug
    2 Posts | Last post August 20, 2013
    • the LESS compiler will generate:
      
      width: -moz-calc(80%) !important;
      width: -webkit-calc(80%) !important;
      width: calc(80%) !important;
      
      when given:
      
      width: -moz-calc(100% - 20px) !important;
      width: -webkit-calc(100% - 20px) !important;
      width: calc(100% - 20px) !important;
      
      Bummer...
      
      rich
    • Problem here too
  • TypeScript comments no longer hiding
    1 Posts | Last post August 13, 2013
    • Anyone know why the typescript comments are no longer hiding from the JS on save.  Also the keep comments flag is gone.  If web essentials no longer is compiling it, how do I tell VS to remove them?
      
      Thanks!
  • About JsDoc of Web Essentials 2012
    1 Posts | Last post August 08, 2013
    • i saw that  Web Essentials 2012 has support for jsDoc intellisense, but I can't seen any options for enabling it, and it doesn't appear to do anything.
  • cant use &:after anymore in less
    1 Posts | Last post August 05, 2013
    • hi, 
      with 2.9 the compiler gives error when using  &:after{} in less
  • Uncaught Error: undefinedModule in V2.9
    3 Posts | Last post August 05, 2013
    • Why my project throw "Uncaught Error: undefinedModule " and "Uncaught ReferenceError: exports is not defined " errors in V2.9? I use dojo with AMD mode. In the old version it's ok, but in the new version I even can't open the project after save code with the configuration " Compile TypeScript on save".  
    • my TypeScript version is 0.8.2
    • I changed to nightly version, and it works fine.
51 - 60 of 328 Items