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.
Related
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.
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.
WEIRD HAPPENING.. I am unable to debug meteor app , BREAKPOINTS doesn't work in chrome(can see the server side sources thou).. I have already wasted 2 days over it ..
I have already tried
Meteor: Debug on server side
Also tried similar options changing web-port and other options.
Also tried to reduce the node-inspector version, BUT breakpoints are not working for me..
any suggestions on how to debug this issue?
(Chrome browser, ubuntu, AMD machine, if that matters)
I have the same issue. The only workaround I've found is to put debugger; statements in my code. Those are respected and treated as breakpoints which stop the server for Node Inspector.
you can try observatory or read this article, maybe it'll helps
You are not alone. There is an issue posted to github about this, and it appears to be confirmed by several users.
I was able to get Node Inspector to work a while ago by downgrading to 1.10. It's not as nice as the new version but worked last time I used it. I honestly haven't needed it recently, but hopefully it'll still work.
I am using VS2010 on Windows XP pro (sp3, x86), and I just installed the hotfix kb2106584. This fix was reported by some people, example here, as having a fix for an issue I had with Asp.Net Development Server not getting opened properly from VS, which I was having previously. My issue was being caused by ESET NOD32 messing with the http traffic from devenv.exe and causing all the ports in my computer to get used up, however.
Anyway, as soon as that was finished, I opened my website back up, and clicked debug. Asp.Net Dev server pops up, which was what the hotfix was supposed to make happen, and then notepad++ opens with the tabs I had last time I used it, and IE never shows up. "Wait, what?" try it again. and again. Always notepad++, never IE, always with no new documents opened, just some completely unrelated stuff.
I've seen one other post on SO about this happening, here, but his issue was corrupted files/filesystem. My project is in source control, so I tried a delete&revert to yesterday's revision. Still opens notepad++, so that's not my issue.
I've also tried rebuilding, which did nothing, and deleting my local Solution files, which also did nothing. I restarted the program and then the computer, both to no avail.
I start to believe that this is the hotfix screwing things up, so I try to do a system restore to a couple days ago. Once again, no dice; it's still pulling up notepad++ instead of IE.
So, the questions become:
Is there a setting or two I can try changing to make it open the proper program again?
Or was this a bad/improper hotfix, and if so, how do I uninstall it? It doesn't show up in the Add/Remove Programs dialog, and I don't see an option to uninstall it in VS, or in the installer.
Thanks in advance.
[edit] Also note: Notepad++ is not actually opening the website file, it's just getting opened with whatever I left in it last time. I dunno if this helps at all, but I felt like details would be appreciated. [/edit]
Fixed:
Uninstalling n++, deleting EVERY registry entry & folder containing 'notepad++' (except one, from whose string I removed ";notepad++.exe"), then reinstalling n++ made VS stop opening notepad++.
Now it opens the default web-browser again.
[edit]
Note for anyone else out there who ends up with this specific and bizarre problem:
It would be worth a shot to try changing the "Browse With..." setting in VS, by r-clicking on Default.aspx to "Internet Explorer". My list included Notepad++ as an available internet browser.
This might be a better solution than the previous, if it does in fact work.
I didn't know this setting would allow Notepad++ as an option until I had to set it back to IE again after all this, and that may have been the problem all along. Apparently, VS just changes this setting sometimes. How or why N++ got put in as an internet browser is completely beyond me, but I did myself the favor of 'Remove'ing NotePad++ from the list, and you may wish to do the same.
Again, I'll never truly know whether or not I nuked everything when I could have changed a single setting that got mysteriously reset, but may this [lesson?] at least be recorded for posterity.
[/edit]
It took all of that to figure out that it [was?] a bogus registry entry somewhere that [may have been?] modified by the hotfix; a registry entry that neither notepad++ nor visual studio 2010 ultimate would clean up on uninstall or replace on reinstall
Which was it? I have no idea. Like I said, I didn't even use n++ this week until VS started opening it for me, and the only change I made was to install that hotfix.
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.