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!)
Hasta el momento he utilizado pocas de sus funciones, pero las que utilicé me parecen sumamente utiles, especialmente las que tienen que ver con CSS. Estas funciones deberían estar de serie en Visual Studio incluso.
Good features but had to uninstall because just typing in .css files became slow en the quick find box took seconds to open and processing a single key-stroke in the QF-box took almost a second. Uninstalling web-essentials fixed this.
I had to disable this extension because it essentially made Ctrl+Comma unresponsive. I've got a web solution with about 47 projects, and I use Ctrl+Comma a lot to jump between files. But with this extension installed, I have to wait up to a minute for files to appear in the Navigate To window. I'm wondering if it has to do with the Ctrl+Comma stuff briefly mentioned in the 2.7 change notes, but I'm not sure.
If I enable JSHint and set the indent option to 2 (or any other number), I don't get any JSHint errors. Other options seem to work fine.
If I enable the option by adding the following to the .js file: /*jshint indent:2 */, then it works, but this is not the solution we want as options should be set in one place, not each JS file. Is there a way to get this indent option working without having to set it in each JS file?
Also it reports errors for switch case indentation, which I believe have been fixed in a newer version of JSHint (2.2.0). Are there any plans to update the version of JSHint used by Web Essentials 2012?
Finally Web Essentials 2013 was updated to use the .jshintrc options file, are there any plans of including this in 2012?
When I select Build | Web Essentials | Update All Bundles I receive an error:
The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG))
I just updated to version 3.3.5 today. Prior to this, the bundles were not updating when a source file changed. They are still not updating and I receive the above error.
I receive the same issue, updating a file does not update the bundled files. This seems to get worse after install update 4 for VS2012. Also, selecting Update All Bundles generates the same error referenced by @jdubsmith
I am using VS 2012 and WE 2012 v3.3.5
I installed visual studio update 4 to see if that would fix it but no luck
I also tried VS 2013 with WE 2013 but it doesnt work there either
It's a great tool, however the current version (3.3.5 with VS2012 update 4 and typescript 0.9.1.1 ) does not created minified js automatically in typescript projects.
I have tried many previous versions of webessentials back to 2.9 and different ways of including the ts and js files into the project, either as DependentUpon liek this
<TypeScriptCompile Include="app.ts" />
or as included on the folder level.
<TypeScriptCompile Include="app.ts" />
<Content Include="app.js" />
When typescript compiles the ts to js, webessentials does not trigger the minification; when I then open the js file and save it manually at some point webesssentials might build the min.js version (eratic as far as I can see), but this will also add the new file to the project tree, from then on webessentials will not update the min.js again. Doing a project rebuild will not automatically minify.
I can reproduce this with the standard typescipt project template.
I just realized, that when manually saving the js file, webessentials will (!) create/update the minified version. But this does not happen when the typscript compiler updates the js file.
This makes it necessary to go manually through all your compiled js files and save them before publishing a release (bundled) project.
Also the js files are not by default included in the typescript project so one first has to include these js files to be able to create the minified versions.
I cannot get a LESS file to minify to .css (and .min.css) in Visual Studio 2013 Premium. I'm using Web Essentials 1.3.1. This was working fine in Visual Studio 2012? Is this a bug? (Note: When I right-click a less file, I see a "Minify CSS file(s)" option, but it's grayed out.)
Having saved ONE FILE (inside of .bundle) WebEssentials saves/updates all other bundles.
11/20/2013 4:23:46 PM: Updating bundle: 1.js
11/20/2013 4:23:47 PM: Updating bundle: 2.js
<here pops an error window about script not found, starting with "/">
11/20/2013 4:23:52 PM: Updating bundle: 1.css
11/20/2013 4:24:16 PM: Updating bundle: 1.js
11/20/2013 4:24:20 PM: Updating bundle: 1.css
If one have over 9000 bundles it will crash everything. Is there a setting to update only *currently* saved bundle-file?
Could be "/" at the beginning of the path related (version 1.3.1 16.11.2013)
It seems as if the version of the coffee compiler included with Essentials is not current. I notice this because up until now we've been using node.js to compile our files. The compiled output of WE seems to include more "safe" local variables and extra spaces you saw from previous coffee versions.
We'd really like to start using WE for compilation but we have a number of users who will still be using node.js on their Macs to compile files. We don't want to have them constantly switching back and forth. Would it be possible to update the version of the included coffee compiler? Better yet, would it be possible to make the compile command an option? This would allow us to specify compilation with node and worry about the coffee version on our own.
It works for me with VS2012 Ultimate with update 3 and v3.0 of web essentials. Initially, it looked like VS wasn't even recognizing the .less file, however, on closing and reopening the file, I got the split view and the generation of the .css and .min.css files also started working.
I just confirmed WHY this is not working. This is also broken with Web Essentials 2013. Our LESS files use the import to import general configuration styles, e.g.,
And then use them later, e.g.,
I commented out all the .mix... imported/pre-configured styles and the CSS file was then updated upon saving the LESS file. Once I re-enabled the .mix... styles, then it hosed again.
Please fix this ASAP as it's a huge hassle. Thanks a lot.
Okay, found more info on this and it looks like it's NOT a WE 2012 or 2013 bug but a change in LESS starting with 1.4.0. Here's the blurb from the 1.4.0 release notes found at http://lesscss.org/#changes
@import-once is removed and is now default behaviour for @import.