I'm currently using Web Essentials 2013 v2.5.3 in VS2013. I use LESS for building my stylesheets.
Up until recently everything regards LESS was working fine, make a change, save and the resulting CSS was updated automatically.
Now for some reason, I intermittently get the behaviour where the resulting CSS is not updated and the following error displays in the VS bottom bar:
Compiling 0 dependent file for style.less
Once the problem starts happening, the only apparent way to fix temporarily is to restart VS. The problem then stops for a while but comes back again at some point later.
I recently installed the Productivity Power Tools (PPT) extension and only noticed this behaviour after that was installed. However I've now disabled PPT and the problem still reoccurs. So this may or may not related.
I've also quite recently tried ReSharper for a while then disabled it some time later so again, that could be related.
Any ideas appreciated.
UPDATE 1 2015-05-14
I noticed that when this happens I'm getting the following message in the "Build" window:
Something went wrong reaching: http://127.0.0.1:62583/?service=LESS&sourceFileName=C:/Path/To/Project/ProjectDir/Content/style.less&targetFileName=C:/Path/To/Project/ProjectDir/Content/style.css&mapFileName=C:/Path/To/Project/ProjectDir/Content/style.css.map&sourceMapURL&autoprefixer&autoprefixerBrowsers=last 5 versions
I've worked out what is causing this to happen. Everything is fine until I attempt to edit and save a JS file. The following is then sent to the Build output window:
Something went wrong reaching: http://127.0.0.1:14886/?service=JSCS&sourceFileName=C:/Path/To/Project/ProjectDir/Scripts/order.js
Any time after that, I get the error message when trying to save the LESS file as well so I'm assuming that whatever is breaking within the JSCS world of Web Essentials is also then causing the LESS compilation to also break.
I've fixed it by effectively almost disabling JSCS using the answer submitted here by Bryan Rayner.
LESS files seem to be back to compiling as normal.
Related
The problem is awkward because everything worked fine. I opened the laptop and somehow it crashed and didn't corresponding to any commands so I had to turn it off. After I started again and after building my project(just in case anything was wrong) and opened my web page I realized that bootstrap is not working at all, and I can't figure out why because I didn't do anything. I tried to install a lower version and didn't worked and after I install the latest stable version and not didn't worked again. If you need any source code let me know and I will edit my post. I will put a picture below which describes what I am talking about(or at least I hope so).
It has the appearance of running in IE Compatibility mode, even though you're on Chrome. Try refreshing your cache (Control+Shift+Delete), rebuilding your project, and using a different browser.
I've run in to this issue before and refreshing the cache usually does the trick.
I have this issue. I have seen others post about the same thing. I have tried every solution that I have found on each post I've seen.
I've cleaned and re-built.
I've gone to the solution properties and updated the configuration to 'Debug' from 'Release' (took several tries to get this to stick).
I've gone through Tools > Options > Debugging > General and unchecked the box for 'Enable Just My Code'.
I've cleaned and rebuilt after each change, then made sure that my change was still in effect before continuing.
With most of these changes it would work once, but when I would close the web page (which I would need to in my testing) and then re-open it the break points would stop working and give me this error. Every time I would come back to see if I could find something else to help. I've run out of options and really need this to work.
This is a project that is using VS 2013, Run in Chrome Version 47.0.2526.106 m, and using .net 4.0. The code is in my desktop, a fresh pull from GIT, I have windows 7 on a dell i7 Optiplex 790.
I am not sure why, but adding a place for caching the symbols allowed them to load. Originally this was blank. Now it seems to be working. Even though it doesn't appear to be actually using the folder I set. I have started and restarted the project a couple of times and the break points will still be hit.
Thanks to #Ernesto I did go through that question, but there wasn't anything there that I had not already tried or that I could try.
So the scenario is that I'm trying to setup TeamCity to check out our ASP.NET solution from an SVN repository and compile it using a Release profile. The checkout from SVN works fine, however compiling the asp.net solution is where things start to fall apart.
The first issue is that TeamCity seems almost bizarrely inconsistent when it comes to compiling. For instance, the first time it checks out the solution and compiles it, everything seems to work fine. However, if I force it to build after that then it gives:
error MSB6006: "aspnet_compiler.exe" exited with code 1.
and fails.
I noticed that this only seemed to be happening on one of the projects in the solution. When I removed the project everything appeared to work fine. Since the above error is no help at all, I resorted to removing parts of the solution until I found the part that (seemingly) was causing the issue.
Initially I was confident that I had identified the problem and so I cleaned everything up and tried to replicate the process from the start. I checked out a clean version and removed the 'problem pages' from the solution straight away. It didn't compile. So I'm scratching my head. It compiled before - why not now?
Anyway by this stage I've burnt a significant amount of time trying to get this up and running. Since the project that it was complaining about was non-critical I just removed the whole thing. So Team City was once again happily building the remaining projects. I leave it alone and move onto the next thing.
I come in the next day and do a force build - and it isn't compiling anymore. It's giving the same error as above but on a different project now!!!
So I'm pulling my hair out trying to work out what's going on here. My questions are:
Why does something that compiles fine in Visual Studio have so many problems in Team City?
Why is the error given by MSBUILD so vague that it's practically useless (and is there any way to get something more useful)?
Why does the solution build fine in Team City one day and not the next?
I recently ran into some strange problems. Changes to files that are not code-behind (and not gets compiled to a DLL) should not require you to recompile the whole website, and this has never been I problem for me. These should actually get compiled dynamically when you first access the resource, e.g. the first time when browsing an updated aspx-page in the browser.
But yesterday, during development of a website, I noticed that even the smallest changes in html, javascript or anything in the .aspx-files doesn't get reflected when I save and reload the page in my browser. Rebuilding doesn't help either, actually I'll have to do a "Rebuild All" (in Visual Studio 2008) in order to see the changes. This applies to all aspx-files in my project.
I tried with minor changes on files in another web application project on the same server, and there it works as it should. Something must has happened to this particular application, but I cannot figure out what.
Do you have any ideas on how to solve this?
Best regards
Not sure if this was the solution, but I noticed that I was running out of disk space. After some cleanup it started working again...
I'm really confused about this problem, and I'm pretty new to Flex. Basically, anything I try to build with mxmlc fails to run now, giving me the above three errors depending on what I do. It was working 30 minutes ago, I've been spending that time trying to figure out what has changed. I redownloaded the Flex SDK, cleared my assetcache, have cleared Firefox's cache. (I'm using Linux.) Even if I compile with -static-link-runtime-shared-libraries=false, since it seems like #2048 is a RSL problem, it still refuses to run.
Another strange thing, if I keep
<policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
<rsl-url>textLayout_1.0.0.595.swz</rsl-url>
in my flex-config file, then firebug tells me that my swf file is trying to access a copy of that in the app's folder, giving error 2032. And if I stick the one I have in frameworks/rsls/ then it gives me error 2046. I don't know how it could not be properly signed, unless Adobe magically changed a signature and didn't update their flex SDK.
Any help will be appreciated.
On Linux I sometimes get these errors. It seems that the Flash Player cache sometimes get corrupt. When I delete the asset cache I then have to reboot in order for things to work again. Not fun. I filed a bug a while back but without having a consistent way to recreate the corruption I can't help them reproduce the issue. Please file a bug if you have a consistent way to reproduce the issue.
Okay, more weirdness. Simply restarting Firefox seems to have allowed the applications to work again. Facepalm
Today I experienced that problem in one browser but not in other. I have Ubuntu 10.04 and in google chrome 6 I received error #2046. In FireFox and Opera everything worked well. The problem has been solved when I reloaded my chrome browser.
This is an off the cuff answer, maybe not correct, but I encountered a similar issue recently and discovered that the issue was that our app was not compiling the Flex libraries into the SWF. Because of this, in some cases the Flash player would for whatever reason decide that the cached Flex libraries (.swz files, aka Runtime Shared Libraries or RSLs) were incorrect versions and so would refuse to load them, giving similar errors without explanation. These cached libraries are separate from the browser cache, they are cached for the whole OS. You could try explicitly linking the Flex libraries into your SWF to troubleshoot the problem. If it goes away, that's a useful clue.