Typescript compiler would stop working. E.g. Making changes to the TS file, saving or even running the program. The generated JS file never picked up the new changes. Attempted to attach a script debugger using 2nd instance of VS2013, could not detect any errors. Almost as if something was knocking the TS compiler out completely. Removed this tool and everything popped back to life again.
Terrible problems after installing this update. My SASS files never compile, I have to keep manually deleting the cache files, and I am just about to re-install for the third time after wasting most of yesterday repairing visual studio.
Same as others, getting .scss SASS files to compile correctly is a nightmare. Just get a bunch of opaque "SCSS: YourFile.scss compilation failed: The service failed to respond to this request, Possible cause: Syntax Error!"
A bit more info would be nice. Files that worked yesterday are broken today. Very frustrating!
Other than that, it's a great tool, but it's very difficult to rely on it.
Chronically plagued by SASS compilation errors which provide no information about their cause and are impossible to correct, forcing you to revert changes back to a state where they did not occur (despite the fact that other SASS compilers have no issues processing the same changes). A source of endless frustration.
Update 2015-04-04 Web Essential 2.5.4 breaks our large Visual Studio 2013 project when we try to use it with VS 2013 Update 4, so we are continuing to use a much older version of both Visual Studio 2013 and Web Essentials. We've pretty much given up hope of ever using Web Essentials 2.5.4 or newer which means we cannot also upgrade everyone on the team to VS 2013 Update 4. We are very disappointed in the pattern of good vs. bug-filled releases because you cannot reliably upgrade a large team to a new version which in turn prevents using the latest VS 2013 update (4 in this case).
Update 2014-11-26 Web Essentials 2.5.3 fixes the issue of not recompiling .less files for me in Visual Studio 2013 Update 4. Small existing project, added two small .js, multi-selected them, WE/Create Bundle, which worked.
Update 2014-11-23 Web Essentials 2.5.2 causes Visual Studio 2013 Update 4 to crash with a null object reference during New/Project/Web/Empty. Even uninstalling WE 2.5.2 doesn't fix the problem. To fix, you also need to run a Repair operation on VS 2013 Update 4.
Web Essentials is getting worse with each new release/patch.
Pros: support a bunch of essential features such as minifying resources, bundle and etc.
I recently started to get the following exception whenever I perform a build on a project:
20.5.2015. 9:50:50: An exception was thrown when Web Essentials: Updating Bundles...: System.NullReferenceException: Object reference not set to an instance of an object.
20.5.2015. 9:50:50: An exception was thrown when Web Essentials: Updating Sprites...: System.NullReferenceException: Object reference not set to an instance of an object.
The exception started to occur recently and the only thing that I've changed is that I've also installed Microsoft Visual Studio 2013 Installer Projects extension (https://visualstudiogallery.msdn.microsoft.com/9abe329c-9bba-44a1-be59-0fbf6151054d) but I do not see how it should be related in any way.
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?!?!?!?!?
Download the install file, then open the file with for example 7zip. Copy the extension.vsixmanifest file to your computer, and change the entry for InstallationTarget to match your version of visual studio. Then save and copy back into the archive (drag into your 7zip window). This is not recommended to do though since it could cause problems (I haven't had any issues so far, but I did it on a test machine).
I'm trying to run some of the sample of SASS 3.3 version code. But it is throws exception while compile.
I'm not sure, what version is used by Web Essentials 2013 Update 4. Can anyone confirm that? Also, it would be great help if I get the guidance to check the Sass version in Web Essentials.
// Variables for 'social network' colours
* Here lies the sexy Sass 3.3 stuff
// The below part is not compiling in VS: Throws Error: "Missing a selector before the comma (',') in a selector group"
$social: (twitter, $Twitter),
Thanks in advance.
Is there any capability to exclude generated files like the .min.css or .css files from being added to the project automatically. I would like to see it where it only builds the files but doesn't add them to the project.
When I start the project and press Ctrl on the browser I see the WE toolbar and everything works (changing Css automatically reflected on the page etc.) however when I want to use the inspect future I see the mouse become + sign but when I hover on the elements on the page it doesn't show the related code in Visual Studio. In all my other solutions this also functions as expected just not this one.
Any ideas what I can check?
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?
We are having the same issue and it is very frustrating. We can no longer trust if our changes to SCSS files are being compiled to CSS files, causing major headaches for developers and testers. Even when opening the file and pressing Save, it is inconsistent. Some developers have gotten into the habit of just pressing Save 10+ times because it may sometimes work.
i believe what happened is i accidentally installed typescript 1.4 as a separate install and this messed it up. i then uninstalled this and rebooted several times, as well as uninstalled and reinstalled web essentials.
any ideas? maybe there's a cache that needs to be cleared somewhere?
been struggling with this all week. any help is appreciated!
The region for js works flowless when no scriptlet is in function, but breaks when it is present.
var x = "<% %>";