The removal of Typescript support is premature. Typescript is excellent, but mostly unusable in its current state without the WE support. WE is still a very good extension with lots of great stuff, but the major reason why I remember to install and use it is now gone. Surely there's a better way of avoiding conflict than by removing useful features now because another team might add them in the future.
Edit: I just found WE2012.v2 in my downloads folder and downgraded. Please bring Typescript support back!
Removal of TypeScript support is a wrong move, imo. VS2012 has really poor support for TS, and I'd rather prefer to turn off VS's Compile-on-save, as it doesn't (always) work anyways, and even when it does - having a side window with generated code view was a huge help. In short - please bring TS support back, at least until VS fixes their stuff. And yes, if you're using TFS in the cloud - this makes things a lot more worse, since now you have to reference TypeScript target for MSBuild, which are not there.
WebEssential 3 is a disaster with the removal of TypeScript support.
The VS2012 update 3 TypeScript features are almost useless. I would STRONGLY recommend against upgrading from WE 2.x if you use TypeScript, especially if like me you use TFS.
Bug 1: 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.
Bug 6: Compiling a web project tries to write to .js file when checked in using TFS, and generates a write error as the files are read-only, whereas WE 2.x will check out the file. The only workaround is to check out ALL files in the web project (AAARGH!)
Hello, it seem IE had a bug with the following syntax:
//@ sourceMappingURL=x.js.map :
When could we expect WebEssential to upgrade to the new syntax :
I am just learning how to use Web Essentials 2012 so maybe this is my inexperience and not a bug, but it doesn't seem like CSS add region is working for me.
1) within a CSS file, on a new line I start typing the letters ad
2) I see the drop down that shows Add region... at the top
3) I have tried several things to get the region to work including:
a. pressing the tab - I just get the word address. The list item Add Region never highlights.
b. pressing the up arrow to select Add Region and then pressing tab. When I do this I get just the word region without the comment marks. I get the same effect when I double click on Add Region.
c. If I manually type the region as shown in the docs like this:
If I do this I get two collapse icons, one next to the first region line and one next to the second comment line. If I don't include the body in comments tag vs highlights it as a css error.
Other features of web essentials seem to be working (like zen coding in HTML). I also tried uninstalling web essentials and re-installing from a fresh download.
Can anyone shed any light on this? Thanks
After upgrading to v2.8 today, any .less files that have @import statements in them are broken. I have found someone else having the same issue, on this stack overflow topic: http://stackoverflow.com/questions/17703093/web-essentials-v2-8-less-import-error/17735609#17735609
I am not receiving any error messages, just a blank preview window, along with blank .css and .min.css files, so my styling is now broken.
Do you have any ideas what is going on?
Unfortunately, I'm having the same issues. In 2012 it appears that the relative path bug has not been fixed, although I can use the @import as far back as one folder (../file.less) I believe. My project structure requires 3 levels up. I tried in 2012.2 and 2012.3.
Using the preview for 2013, no @import works. This is such a great addition to Visual Studio, it's such a shame that one single item keeps bogging me down.
When I write:
The css is compiled but #normalize is "undeclared.
#normalize is declared but the css doesn't compile.
After I upgraded to 2012.3 update (I think it's related), my LESS intellisense and syntax highlighting stopped working. web essentials apparently still work, as I can still see CSS preview (correctly syntax highlighted), LESS compiles and I can change options.
I just upgraded to 2.8 hoping this has been resolved, but I can see the same effect. No LESS highlighting nor intellisense.
Visual Studio 2012 Update 2
Web Essentials 2.7
Every time when I try to change or create any .less file, I got this message in css preview:
See error list for details
And when I open Error List, I can see this:
This thing same everytime, no description at all. It doesn't depend from code, even this code generate error:
What shell I do?