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 get this error:
Microsoft Visual Studio
Not implemented (Exception from HRESULT: 0x80004001 (E_NOTIMPL))
I work in an environment where we have very limited permissions on our computer. I installed Web Essentials 2012 and created a blank .less file. The preview window is showing
Compile Error. See error list for details
I pulled up the error list and it's showing
LESS: Permission denied
I can't find the error in any log or the event viewer so I don't know which account needs permissions to what folder. I tried giving everyone all permissions to the folder that contains the .less file just to see if that was where the error is, but that didn't do it. Does anybody know which folder it writes to? The temp asp.net folder maybe? Do you also know what account needs permissions? I don't have rights to modify the temp asp folder, so I'd have to put in a request with my IT department, so I can't really just play around and figure it out via trial and error.
I've spent a few days trying to find an answer to this, but I'm not getting anywhere. If someone could point me in the right direction, that would be awesome.
When you compile a not valid SASS files a Link Error is generated.
This link is not connected to a running Web server.
How can I customize this link.
Something went wrong reaching: http://127.0.0.1:6642/?service=SCSS&sourceFileName=C:%5CWork%5CMCH.CMS.Sass%5CMCH.CMS.Sass%5Cproject%5CCongress%5CBuehne%5Cportalbuehne_did.scss&targetFileName=C:%5CWork%5CMCH.CMS.Sass%5CMCH.CMS.Sass%5Cproject%5CCongress%5CBuehne%5Cportalbuehne_did.css&mapFileName=C:%5CWork%5CMCH.CMS.Sass%5CMCH.CMS.Sass%5Cproject%5CCongress%5CBuehne%5Cportalbuehne_did.css.map&precision=5&outputStyle=expanded&sourceMapURL&
Recompile all less files worked just fine, but when I've checkout fresh version into another folder it stop working (including recompile after build).
If I open less file, change it and save (css is created) then this file works automatically since then just fine.
Should I open each time I create a new repository all less files, or there is another way?
The only way, find out for now is to commit .css files too. Though all my .css files are autogenerated and therefore it is a pitty, that I should commit .css along with .less and checkin .css on change of less too.
So, after clicking one-click publishing, I see this in my output put window in VS2012:
========== Build: 1 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Publish: 1 succeeded, 0 failed, 0 skipped ==========
9/10/2014 3:15:40 PM: ImportMixins.less compiled
9/10/2014 3:15:40 PM: rs-ui-tabs-from-bulleted-list.less compiled
9/10/2014 3:15:40 PM: ImportVariables.less compiled
9/10/2014 3:15:40 PM: variables.less compiled
9/10/2014 3:15:40 PM: rs-custom-controls.less compiled
This appears to me to be compiling LESS files after publishing my site.
Is there a way to ensure compilation before publishing other than doing a manual build prior to hitting publish?
I am having this issue now as well. I have one site.scss file that imports various other partials. It was working fine until a few days ago when (seemingly) at random they started failing to compile on save. Now the partials require the other partials to be imported into them before they will compile. I've triple-checked my @import flow and it is perfect! Sassmeister and other compilers have no issue.
Specifically, I get the "unparsable compilation error" as well as meaningless "(X)101" errors in the Error List. No line numbers or suggestions to be found.
Any help would be greatly appreciated!