in IE11 I display the developer tools, then click on the debugger (or Ctrl-3) and it displays the debugger. In the top left there is the folder drop down which has a list of js files usually, but in this case none are displayed, only the html file is displayed.
The site I'm looking at is on my local PC running in IIS if it matters. I can go to the same site on our build box and the js files are displayed in the debugger. I've restarted everything a number of times. I've checked the network monitor in the developer tools and it downloads the javascript files fine, I just can't see them in the debugger. It's worked previously fine (a couple of weeks ago when last I had to debug an IE problem), Any suggestions?
running IE 11, Windows 7
Go to Internet Options -> Advanced. Uncheck Disable script debugging, Disable script debugging (Others)
Must be a problem with my IE11 install - I downloaded an IE11 vm from modern.ie and it works fine there. (setup information here for any curious https://superuser.com/questions/248569/virtual-pc-cant-access-localhost)
Please go to the Debugger tab in Developer tools. Hit Ctrl+O and type your file name.
Alternately, you can click the Folder icon and search for your file.
Related
I'm having an issue debugging a simple web app in Google Chrome 87 with Visual Studio 2019 (16.7.1). The debugger starts and Chrome opens fine. When I open Dev Tools (F12) and go to the Network tab, I can see all of the HTML, JS, images, etc. just fine. If I click any entry except for an HTML file, I can see the Headers, Preview, Response, etc. for the file. If I click any HTML file, Chrome completely freezes and I have to shut down the browser/end the debugging session.
I noticed if I end the "Node.js: Server-side JavaScript" task in Task Manager while Chrome is locked/frozen, Chrome immediately un-freezes and I can debug again. What could be causing this issue? If I restart the debug session, the Node.js task automatically starts again.
Clicking the highlighted entry causes Chrome to freeze:
Ending the Node.js task un-freezes Chrome:
Try the following steps to troubleshoot the issue:
Normally startup VS
1) disable any third party installed VS extensions under Extensions-->Manage Extensions-->Installed
2) reset all vs settings under Tools-->Import and Export Settings-->Reset all settings. Also, you could make a backup of your settings
3) Delete all temporary files under C:\Windows\Microsoft.NET\Framework\vx.x.xxx\Temporary ASP.NET Files
4) close VS, delete .vs hidden folder, bin and obj folder. After that, restart your project, build, try to debug again.
5) also, if you select Silverlight Debug, please disable it. See this link.
6) try another preview like IE or Edge.
7) If not, just delete the whole folder C:\Users\xxx\AppData\Local\Microsoft\VisualStudio\16.0_xxx or rename it. Make a initial environment for VS, then restart VS to test again.
8) repair vs or update it to the latest version
Go to Inspect > Network > Network Throttling dropdown > set it to 'No throttling'.
I'm running an application on jBoss.
In one page there are many js files. Chrome and Firefox see the changes on all js file when I reload the page, except one.
I open Chrome (firefox) in unknown mode, disabled the cache of Chrome console (Firefox console), reload the page, clean and restart the application server and rebuild the application.
Nothing.
I don't know what to do.
When linking the scripts on you pages you can put something after the file like
<script language="JavaScript" src="<file_name.js>?yyyymmdd"></script>.
This "yyyymmdd" can be the current Date/datetime (never caches) or the last modification date of the js file you are including (it cancel the cache only when you modify the script).
That is the approach we use.
In chrome, go to developer tools(press F12), go to Network panel, there check 'Disable cache' option and load your page..
I'm developing a webapplication (asp.net mvc 4) with Microsoft Visual Studio 2012, and as the solution is getting bigger, the debug is getting slower.
Need to know if there is a way to debug only my client side (javascript) on visual studio instead of the entire application (server+client).
Is there any way to attach to process of IE and get the breakpoints working ....?
Not interested on get the debugger running on entire client/server application, just client.
First open Visual studio ..select your project in solution explorer..Right click and choose option "browse with" then set IE as default browser.
Now open IE ..go to
Tools >> Internet option >> Advance>> uncheck the checkbox having "Disable Script Debugging (Internet Explorer). and then click Apply and OK and you are done ..
Now you can set breakpoints in your JS file and then hit the debug button in VS..
EDIT:- For asp.net web application right click on the page which is your startup page(say default.aspx) and perform the same steps. :)
Yes you can put the break-point on client side page in Visual studio
First Put the debugger in java-script code and run the page in browser
debugger
After that open your page in browser and view the inspect element you see the following view
The debugger should automatically attach to the browser with Visual Studio 2012. You can use the debugger keyword to halt at a certain point in the application or use the breakpoints directly inside VS.
You can also detatch the default debugger in Visual Studio and use the Developer Tools which come pre loaded with Internet Explorer or FireBug etc.
To do this goto Visual Studio -> Debug -> Detatch All and then click Start debugging in Internet Explorer. You can then set breakpoints at this level.
For debugging JavaScript code in VS2015, there is no need for
Enabling script debugging in IE Options -> Advanced tab
Writing debugger statement in JavaScript code
Attaching IE didn't work, but here is a workaround.
Select IE
and press F5. This will attach both worker process and IE as shown here-
If you are not interested in debugging server code, detach it from Processes window.
You will still face the slowness when you press F5 and all your server code compiles and loads up in VS. Note that you can detach and attach again the IE instance launched from VS. JavaScript breakpoints are hit the same way they are in server side code.
It is possible to debug by writing key word "debugger" to place where you want to debug and just press F5 key to debug JavaScript code.
http://www.aspsnippets.com/Articles/Debug-JavaScript-and-jQuery-using-Visual-Studio-in-Internet-Explorer-browser.aspx
This is what worked for me:
Add a new browser with to ie x86 version
2- On the Start Options of the Property Pages select the Start Option as:
Don't open a page. Wait for a request from an external application
3- Open the application from internet explorer
4- In the attach to Process screen select the following code types:
Javascript (Microsoft edge - chromium) and Script
5 - In the available process list select:
iexplorer.exe x86
I'm working on developing a site on my local machine (Windows 7 Ultimate x64) using WAMP, running APACHE v2.2.22, PHP 5.3.13, and MySQL v5.5.24. I'm developing using Chrome v 22.0.1229.94. I've got quite a bit of javascript in the site, however, and Chrome is relentlessly blocking javascript from running on the page.
Clicking on the little 'blocked javascript on this page' icon in the address bar includes the dropdown that has "Always allow Javascript on Localhost" checked off, and I also have a JavaScript exception in Chrome's settings explicitly saying to always allow JavaScript on 'http://localhost'.
Cookies are being allowed, "Allow all sites to run JavaScript" is checked off, and I have no idea as to why Chrome is not allowing the JavaScript to run.
Overall, it's not imperative to the project that I figure out a fix as both IE9 and Firefox 16.1 are allowing JavaScript and I can utilize them. I am simply curious if there's anything I can do to fix this in Chrome, as I would like to continue developing in Chrome.
If you notice that JavaScript is only blocked when the console is open (as some are saying), chances are that you disabled JavaScript in the console settings.
Open the console.
Click the vertical ellipsis icon (or the gear icon on older versions) in the upper right and go to settings.
See if the "Disable JavaScript" checkbox is checked.
I have the same issue, but only when the console is open. When the console is closed, JavaScript loads fine on localhost. Makes it hard to debug things though....
I got around it by opening localhost in an incognito window.
You can give your local server a domain name, may be that would help.
Open C:\Windows\System32\drivers\etc\hosts in notepad
Edit that file add a new line at the end
127.0.0.1 mydomain.com
Save, now goto chrome and type in http://mydomain.com/ this should point to your local server.
Since you nolonger run on "localhost" may be chrome will let you pass.
Let's me know if that works. Good luck!
I'm having a really annoying problem with debugging javascript with VS2008.
If I simply press F5 (or choose 'start Debugging' from the Debug menu), the iexplore process is attached, but no breakpoints break in the scripts. The Script Documents tree doesn't even appear in the solution explorer.
I already know:
I can set a breakpoint in Javascript just fine. It does NOT show the "This point will not be hit" message.
Calling the debugger through using the 'debugger' keyword works fine, but attaching to the iexplore process doesn't since it gives a "process already attached to a debugger" message.
Using the manual 'Attach to process...' works just fine. The Script Documents appears as well.
The project has recently been converted to a Web Application from a WebSite.
I already tried:
Clearing the IE cache.
Shutting down VS2008, Stopping the IIS and deleting the temporary asp.NET files restarting both IIS and VS2008 afterwards.
Setting IE7 as the default browser both for windows and for VS2008.
Resetting my user settings for VS2008.
Checking that IE script debugging is enabled.
Nothing has worked so far. While Attaching to process isn't too taxing, it is very annoying when I'm used to just hitting F5.
If anyone can think of a solution, please please please (I'm begging here!) let me know!
Is silverlight debugging enabled on the website project properties? This will disable Javascript debugging.