I just upgraded to v3.1 and I'm seeing bizarre behavior when I open Markdown files (*.md). I can't select text with the mouse and I can't type any characters, but I can move the cursor with the arrow keys and the Enter key will add a new line. It's basically unusable on my machine right now.
Web Essentials 2012 doesn't seem to handle the LESS concept of marking mixins an important.
Doing something like this:
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.
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'.
Does anyone knows how to fix it? Is this a known issue?
We can't use Web Essentials 3 because the TypeScript support in VS2012 is worse than useless.
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.
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
No longer creates both .min.js and .js files - VS2012 just creates a .js file with no option for a .min.js file
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.
Compiling a web project tries to recompile .TS files - and there is no option to turn this off. See also bug 1.
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.
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?
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?
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.
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.