Is there a way to make a squiggly line go away without changing my code? I understand that there are more vendor prefixes I could use, but if my project is only supporting webkit, I would REALLY like to make that squiggly line go away. Please, please, PLEASE put an option to ignore or even an option to disable "alert for vendor prefixes" in the future.
I firmly believe that any squiggly line that comes up in anything should be able to be removed after user consideration. I know this is a great extension, but just like Microsoft Word doesn't always have better grammar than I do, this extension should take my input.
Thank you for the phenomenal extension and all your hard work!! :)
In version 2.2 you can select which browsers to support and the CSS editor will adjust accordingly with the correct validation and auto-generated vendor specifics. Just right-click in the CSS editor to open the browser selector
There seems to be an issue in the Zen Coding support with lists containing sibling elements. e.g. div>ul>li*5>span+div only adds the nested div to the first li, and not the other 4. Nesting the sibling elements in a container div doesn’t work either (div>ul>li*5>div>span+div).
I would give this 5 stars, but as an licensed Mindscape user, I think I will need to disable WE 2012. The reason is, while I can disable compiling and previewing LESS from WE, it still messes with the syntax highlighting and parsing of the LESS files (since that's what Mindscape does).
Mads, I would give you 10 stars if you could either a) detect Mindscape and prompt/automatically disable LESS handling or b) allow me to fully disable LESS handling in WE options.
It should be noted also, I work on a team, so it would also be nice to save a local set of WE settings or something (which is why I mentioned automatically disabling LESS handling).
Unfortunately, I can't turn off LESS editor support dynamically. We (the ASP.NET team) is shipping the LESS editor officially early 2013. That can't be turned off either. Is there a reason you prefer Mindscape's LESS editor over Web Essentials'?
I've just released new LESS editor component in the nightly build. Try it here: http://madskristensen.net/post/Web-Essentials-nightly-builds.aspx
Local WE settings are supported and so are solution based settings. That was introduced in version 1.9
So far, Web Essentials has been a very useful and productive tool. It makes VS that much better, and I'm surprised half of the functionality isn't already integrated into the core VS application. I like the flexibility of the plugin though and quick responses to bugs and features.
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!
I just installed this extension looking for this awesome functionality. Unfortunately, I can not create a image sprite from my images. The option directly does not appears at context menu. I don't know how to enable it. Am I forgetting any step after installing the extension?
I am working with VS Professional 2012 (Update 4), and ASP.NET Web Frameworks and Tools 2013.1.
Thank you so much for your time and efforts!
First off, great tool you are providing. Have made my network footprint as small as possible.
First problem i noticed was that when i enabled JS Minification, the *.map files were getting 404 responses. After review of the *.min.js file i noticed that the Mapping URL line did not include the folder directory they were located.
Had to add the folder to the 'sourceMappingURL' in order to not get the 404:
Not sure if its possible but might be well worth looking into it for 2013, if not 2012 update.