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!)
first of all...your WebEssentials are great!
How could I tell jsHint to ignore a couple of files(third party stuff)?
It seems, that jsHint does not recognises .jshintignore at the root of my project.
Did you integrated any other solution?
Web Essentials rocks... but it would rock even more if we could automagically create .d.ts files (via the --declaration command line option). This would solve a long-standing issue with having to have tons of files checked out to even save a .ts file (with references) and may even go some way to speeding up opening and building our solution.
Pretty please with cherries on top :)
1. It doesn't seem to be playing nice with some of the new generics, reporting errors where there are none:
// using latest knockout.d.ts
var portText = ko.observable("");
portText(""); // this line generates the error: "Could not select overload for 'call' expression." It compiles error free and executes fine tho.
The compiler doesn't complain, but the IDE underlines the code in red and appears in the "Error List" section.
The sources property in the generated .map file seems to always include the relative path from the root of the server. The problem is that our applications use virtual directories and therefore these references don't work when trying to debug from the browser. It all seems unnecessary too since the bundling is happening at a folder level so you could always assume the reference is relative to the map file. We are having to add a post build step to fix our references in the "sources" property after each time Web Essentials messes them up.
Other than that, great job ;)
I've just noticed that in my sln tree the icons of .ts-files became 'media-playerish' (old-style 'film' icon with the 'play' sign on it), and the same time Web Essentials seems to know nothing of the .ts-files. Symptoms:
- ts-files are opened in VS by plain text editor; no intellisense, no generation on save;
- no generation on build if set;
How to fix it? Reinstalling of WE didn't help. Nor did setting Windows file '.ts' association from Media Player to VS.
In my project I have the following directories :
component.less contains the following style :
background: url(../images/triangle_v3_top.png) no-repeat;
The component.less file is imported in core.less :
In the core.css file generated I have this :
background: url(composants\../images/triangle_v3_bottom.png) no-repeat;
The backgroug url is wrong, it must be :
background: url(../images/triangle_v3_bottom.png) no-repeat;
When I use Prepros to build less file (http://alphapixels.com/prepros/) the url is correct.
I have a CSS bundle and no matter what I try, it won't update. When I make modifications to a .less file and save it, the corresponding .css file is updated. Then I try to build the website or I go the to Web Essentials menu under BUILD and select "update all bundles" but nothing happens.
I had a similar issue but with just the minified versions of the bundles. For me, if I removed one of the <file> entries from the .bundle file, saved, then added it again, the bundle would get updated properly. Hope it helps!