Pros: support a bunch of essential features such as minifying resources, bundle and etc.
P.S. I used this plugin for 3 years on 2 version of VS in 4 locations before uninstalling it. Let me know if you improve the plugin.
VS2013 U4, WE 2.5.3 (but any 2.5.x has the same problem), clasical webproject on IIS express, .NET4, build completely fails.
An exception was thrown when Web Essentials: Updating Bundles...: System.NullReferenceException: Object reference not set to an instance of an object. at MadsKristensen.EditorExtensions.BundleFilesMenu.<UpdateAllBundlesAsync>d__12.MoveNext() An exception was thrown when Web Essentials: Updating Sprites...: System.NullReferenceException: Object reference not set to an instance of an object. at MadsKristensen.EditorExtensions.Images.SpriteImageMenu.<UpdateAllSpritesAsync>d__f.MoveNext()
If I use the non-minified version, Angular breaks because of variable names (the dependency inject fails). I know I can send a array with dependency names, but those libs are not mine (and I can't change the source).
If I use the minified version of those libs, the mapping comments points to the original folder (and thus, chrome won't find the .js.map file because the bundle is in another place). This happens because Web Essentials will only concatenate those .min.js, but those files points to some .js.map and Web Essentials doesn't fix those paths!
So my questions are:
1) There is some way to config Web Essentials minification process to not change arguments names?
2) There is some way to fix the map for existing files?
I work in an environment where we have very limited permissions on my computer. I installed Web Essentials 2012 and created a blank .less file. The preview window is showing
Compile Error. See error list for details
I pulled up the error list and it's showing
LESS: Permission denied
I can't find the error in any log or the event viewer so I don't know which account needs permissions to what folder. I tried giving everyone all permissions to the folder that contains the .less file just to see if that was where the error is, but that didn't do it. Does anybody know which folder it writes to? The temp asp.net folder maybe? Do you also know what account needs permissions? I don't have rights to modify the temp asp folder, so I'd have to put in a request with my IT department, so I can't really just play around and figure it out via trial and error.
I've spent a few days trying to find an answer to this, but I'm not getting anywhere. If someone could point me in the right direction, that would be awesome.
Having this main.less file with only one line of import:
@import (inline) '../../Content/bootstrap.css';
cause an exception:
3/12/2015 13:51:28: LESS: Compiling main.less
3/12/2015 13:51:28: LESS: main.less compiled.
3/12/2015 13:51:28: An exception was thrown when updating TextView property: System.NotSupportedException: The given path's format is not supported.
at System.Security.Util.StringExpressionSet.CanonicalizePath(String path, Boolean needFullPath)...
The moment I installed it, VS stopped recognizing any and all of my custom classes. None of the models in my MVC project would work anymore and the editor considered them broken references. It would still compile, strangely enough, but it would get the little red squiggly lines and none of the menus that pop up every time I hit the "." key anymore.
If I disable the extension, everything works just fine again.
I've been working on a problem all day. I'm close to the answer.
Suddenly I start getting JSCS errors that prevent my project from running.
I'm happy to go back and make all the little changes JSCS seems to want but I don't think I should be making so many changes when I'm troubleshooting. I need to fix the problem I started working on and then go back and try to satisfy JSCS.
I'm searched all over the internet and found ways to make JSCS ignore all my JS files but these options don't seem to work. IE: "excludeFiles": ["/**"],
I just want to run my project so I can fix my problems. I'm ok with the 23 Messages I'm getting from JSCS and I appreciate it. What I don't appreciate is my project not running because these message are interpreted as build errors.
How do I turn this off so that message are only messages or treated like warnings and not build errors?
I have WE 2013 Updt 4 installed. I have bootstrap less files in my project. right clicking on any of them: entire WE context menu is greyed out. nuts. on VS Menu bar is WE, I select "Re-compile LESS files" nothing happens. What the heck is going on? Does this thing require node to be running? does it require a sacrificial virgin? is there any documentation anywhere?
hours of frustration, and one p*ssed client waiting for me. Help?
this is not clear at all.
I've Visual Studio 2013, but "Update 5 ctp".
If I try to install the Web Essentials 2013 I get: "This extension is not installable on any currently installed products";
and if I try to install the Web Essentials 2015 I get: "This extension is not installable on any currently installed products";
So... how am I supposed to install this Web Essentials?!?!?!?!?
When re-compiling all SCSS files in our project (277 files), some will always report errors (with the Something went wrong reaching: syntax). Compiling them by hand will then success or fail inconsistently. Killing all node.exe processes and then compiling by hand will succeed.
This way there is no way, except by compiling 277 files by hand, to check if all the scss files are still correct. Is there a way around this?
But in most of the Microsoft Demos I see another solution by using a bundle.config, having a "BundleConfig.cs" and calling RegisterBundles(BundleCollection bundles) from Global.asax.cs etc. Here I think everything is generated during compile time (if I am not mistaken)
It looks like that there are two very different approches. First: Why :-) ? Second: What are the advantages and disadvantages of both approaches? Is one newer than the other, is only one future-proof?
Thank you for clarification!