Web Essentials 2012

Free

Adds many useful features to Visual Studio for web developers.

(192) Review
Visual Studio
2012
Download (1,093,691)
9/10/2014
3.8
View
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Description
Reviews (192)
Q and A (325)
Sign in to write a review
Sort by:

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 | November 30 2013

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

by HiTech Magic | October 22 2013

Dropping support for TypeScript (without plastering that "little" detail all over the download page) has just cost me 4 wasted hours and sent me full circle back to the old Web Essentials.

1. Installed Web essential update
- lost TypeScript support

2. Installed separate TypeScript add-in from MS
- Does not build existing TypeScript files in project

3. Researched how to modify project to get it to build TypeScript files
- Still does not build existing TypeScript files in project

4. Created a new project minimal testbed to test TypeScript compiling
- ts files are added, with TypeScriptCompile option, but do not generate .js files at all. Tools | Options etc have no effect

5. Researched this new problem
- Gave up in disgust

6. Uninstalled TypeScript & latest Web Essentials

7. Installed old Web Essentials
- Luckily this was still in my download folder

8. Have now lost color-coding, intellisense and all those other features that made Web Essentials useful.
- Decide to write grumpy review :(

I have never had so much grief from one update. In future I will Google for problems with the updates before even thinking about pressing upgrade!

by Cattousa | October 15 2013

WebEssentials 2012 is a stellar extension. Being able to collapse JavaScript between {curly brackets} is very useful.

by Ytrog | October 15 2013

Good plugin although the CoffeeScript functionality doesn't compile the scripts and crashes vs2012 every time I try :(

by Aleksandar Totovic | October 08 2013

It's very nice

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


  • LESS mixins marked as !important not supported?
    3 Posts | Last post October 09, 2013
    • Hi!
      
      Web Essentials 2012 doesn't seem to handle the LESS concept of marking mixins an important.
      
      Doing something like this:
      .input-validation-error {
      	.inputHighlight(@red) !important;
      }
      
      Gives the following warning:
      Missing a property name before the colon (':') in the "(property) : (value)" declaration.
      
      And when I compile the following error:
      LESS: 'undefined' is null or not an object
      
      I'm using version 2.6.
    • Same experience. 
    • If the compiler gives an error, then it must be an error since it's the official LESS compiler being used by Web Essentials. Are you sure this is valid LESS?
  • How to report bugs for this tool?
    2 Posts | Last post October 09, 2013
    • The link to report bugs for this extension is unavailable.
    • Sorry about that. It has now been fixed
  • Cannot Access Disposed Object error after installing this extension
    1 Posts | Last post October 04, 2013
    • After this extension was installed, I started receiving the following errors from Visual Studio:
      
      ---------------------------
      Microsoft Visual Studio
      ---------------------------
      Cannot access a disposed object.
      
      Object name: 'MarshalingWindowFrame'.
      ---------------------------
      OK   
      ---------------------------
      
      Does anyone knows how to fix it? Is this a known issue?
  • Can we put TypeScript support back in please???
    2 Posts | Last post September 27, 2013
    • We can't use Web Essentials 3 because the TypeScript support in VS2012 is worse than useless.
      
      Bug 1
      
      VS2012 TypeScript Compile-on-Save feature does not work. If you create a new TypeScript file and save it, VS does not compile on save.
      
      Bug 2
      
      No side-by-side JS window - now you've got to go hunting for the JS file to figure out if the file got compiled or not
      
      Bug 3
      
      No longer creates both .min.js and .js files - VS2012 just creates a .js file with no option for a .min.js file
      
      Bug 4
      
      Created .js files don't get added to the solution. We check in our compiled .js/.min.js files, which WE 2.x did automatically. VS2012 does not do this.
      
      Bug 5
      
      Compiling a web project tries to recompile .TS files - and there is no option to turn this off. See also bug 1.
      
      Bug 6
      
      Compiling a web project tries to write to .js file (see bug 5). If the .js file is checked in using TFS, it generates a write error as the files are read-only, whereas WE 2.x will check out the file (ie. it is TFS-aware). The only workaround I have found is to check out ALL files in the web project (AAARGH!)
      
      PLEASE put TypeScript support back in! We are reverting to version 2.
    • I have to agree: the TypeScript move in 3.0 was really terrible. I don't quite see how I'm going to be able to keep using TypeScript with 3.0. It seems as though the integration of the new TS version with VS is just half assed :(
      
      Switching back to 2.7, fingers crossed I haven't permanently messed things up now.
  • LESS Compiling great but minification breaks CSS
    1 Posts | Last post September 03, 2013
    • I'm being using Web Essentials 2012 now for a couple of months and it has been great. I recently started using LESS and am having  strange issue.
      
      The LESS file complies great on save and if I used this compiled .css file my site works as intended. I also have it set to minify on save. If I use this .min.css file the whole site breaks. It appears more than half of the file is ignored in all browsers. I don't see anything odd in the output. Looking in Chrome developer tools and looking at the loaded resource, about 1/8th of the way through, the syntax highlighting turns off, anything that isn't highlighted (plain black text) does not work on the site.
      
      Has anyone experienced this type of behavior before?
  • Command line tool for script bundling?
    1 Posts | Last post September 03, 2013
    • Web Essentials works great locally for bundling and minification, but I need to ensure that the bundle is generated on the server build rather than locally (I'd rather not check in a generated file).  Is there an associated tool I can run to generate the bundle on the server build?
  • LESS Compiler crashes Visual Studio
    1 Posts | Last post September 01, 2013
    • Using Visual Studio 2012.3 and Web Essentials 2010 3.0 my Visual Studio crashes every time at try to save a .less file.
      I guess it is the less compiler that causes this - anyone knows a fix for that ?
  • 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
41 - 50 of 325 Items