I just installed VS2008 on a brand new Win7 machine and have started at a new company. I am now running the company's main project and all is well...except that, for some reason, .Net keeps breaking on some javascript errors. This isn't in the browser (although it only happens when running IE, in this case version 8).
I'm at a loss as to where to find the option to turn off the javascript debugging in VS 2008.
Can anyone point me in the right direction?
The setting is actually in IE.
Tool -> Internet Options -> Advanced
Under browsing
Check Disable Script Debugging.
Related
I am developing a web application on Visual Studio 2013. On older versions, whenever there is a bug in the web app, I moved from the browser to the visual studio to the line where the code is.
Now, whenever there is a bug, I just see it in the browser without being able to see it in the Visual Studio. As if the debugger is not able to step into my code.
This has been going on for all my web projects which makes me feel that it is a setting in VS but I am not able to locate it.
can anyone help?
I was able to find out what was wrong here.
it seems that for some reason, under Debug in the main menu and under Exceptions, nothing was checked! I checked ALL "Common Language Run-time Exceptions" and it worked for me.
However, you need to spend sometime there in the debugging list. If you enable ALL, you will get all sort of exceptions captured.
I have an ASP.NET web site created with WebMatrix 3. I do have the option in VS2013 checked to use the 64-bit version of IIS Express since I am running on 64-bit Windows 8.1. When I try to launch the project I get the error "An operation is not legal in the current state". Does anybody know how to fix this?
I got this same error "An operation is not legal in the current state" when running a project on Google Chrome, Stopping the project then closing all chrome instances fixed the problem.
I think it's related to visual studio not being able to attach to chrome instance for debugging.
Closing Chrome and restarting IIS (e.g. in IIS Manager) should solve the issue. It helped in my case.
Just had the same issue on VS (Visual Studio) 2017 this morning.
The steps that will resolve this are:
Stop project that runs in VS
Clean all IIS instances that VS temporarily created
Compile project and start that service again
i am using IIS in a visual studio 2010 solution with Integrated 4.0 and 2.0 Classic web pools. when i use IE 11 over the Inet to "try" and login, the app fails.
yes i know about changing settings but this cannot happen on my web site. Any thoughts on what is happening and / or why?
i have not tried to bring up the app using IE 11, any ideas on the "surprises" i will find? thanks for any comments, they are appreciated.
I had the same issue using VS2010. I knew this problem existed with IE 10 and I somehow let the automatic updates install IE 11.
I found this fix from MS and it resolved the issue for me:
http://blogs.msdn.com/b/visualstudioalm/archive/2013/09/17/coded-ui-mtm-issues-on-internet-explorer-with-kb2870699.aspx
My apologies if this is wide of the OP's question, but I also had problems using Studio 2010 with the new IE 11 (googling those two terms led me here, and John B's post led me to answer). Specifically Studio's debugger would fail to attach to IE 11 while I was launching a Silverlight project.
John B linked to an MSDN patch. After I installed it, Studio still would fail to attach to IE11, but at least this time I got an error message: "The 32-bit version of the Visual Studio Remote Debugging Monitor (MSVSMON.EXE) cannot be used to debug 64-bit processes or 64-bit dumps. Please use the 64-bit version instead."
From that message I found out that Silverlight can only run in 32-bit mode. And both IE10 and IE11 cannot run in 32-bit mode when they place all the tabs into a single 64-bit process. However, if "Enhanced Protected Mode" is enabled (which it was for me by default, it's under Internet Options' Security tab) and you change this registry value...
HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\TabProcGrowth
...to be something more than 0 (I set mine to 5, not sure it matters much as long as it's more than 0), then IE11 is able to spawn 32-bit processes and Studio is able to launch a 32-bit browser instance that it can attach the Silverlight debugger to.
A few related articles...
http://support.microsoft.com/kb/2716529
https://superuser.com/questions/561036/unable-to-open-ie-10-in-32-bit-mode
http://connect.microsoft.com/VisualStudio/feedback/details/774460/cannot-debug-silverlight-win7-x64-ie10
Hope this helps someone.
I'm developing an ASP.NET MVC 4 site using Visual Studio 2012 Premium on Windows 8 RTM x64. When I right click on the web application and choose Publish, Visual Studio 2012 returns the message:
"fail to open url of 'http://.../'.
Exception:Class not registered"
The publish process seems to work correctly but it fails to launch the browser. This happens every time I try to Publish the site and it happens with Chrome (21.0.1180.79 m) or Firefox (14.0.1).
Furthermore, since the site isn't launching post Publish, I do it manually using Ctrl-F5. I'm able to navigate around the site normally, but if I right click on the browser's icon on the task bar to launch another browser instance, nothing happens. Once I close all browser instances, the browser task bar icon reverts to its normal behavior.
I'm not sure if these two issues are related, but the common theme here is launching a browser from Visual Studio 2012 causes unexpected side effects. The browser either fails to launch on Publish or launches with Ctrl-F5 but renders launching another instance useless using the task bar icon.
Any help is appreciated.
EDIT: I've re-installed the entire software stack (Windows 8, Office 2010, Visual Studio 2012, Windows Update, Chrome, Firefox). The above issues continue, unless I make Internet Explorer the default browser.
Thanks.
I filed a Chrome bug, it was a browser registration thing. If you uninstall and reinstall from a Download and be SURE to say Yes to the UAC prompt, Chrome will register Machine Wide, rather than User. That is required to launch as Admin. (HKLM vs. HKCU)
It appears this problem is much more widespread than the Web Publish operation. Anytime you use the ShellExecute() API (or Process.Start) to access a URL it fails when running under elevated rights (ie. Run As Administrator).
I see this in any application that uses Process.Start() or ShellExecute(). When UAC is on and I run it normally under the UAC account everything works and the browser opens. Run with "Run As Administrator" it fails. It's easy to test.
Not sure if this is a bug in the OS, or whether Microsoft deems this as a security 'feature'.
FWIW, some people have mentioned the setting IE as the default browser works, but it doesn't work for me. Basically no links work if I've elevated rights. This has actually broken quite a few administrative applications we use in the back office for administration.
I'm trying to debug an ASP.NET 3.5 app, which I've recently migrated from VS 2005. (This uses Crystal Reports 11 Release 2, but I don't know if that comes into what's causing me problems, or not.) This app uses Active Directory for authentication. I'll have the app opened in VS 2008, and then press the F5 key to start debugging. Shortly after that VS 2010's Just-In-Time debugger pops up and asked me if I want to (a) debug w3wp.exe, of (b) cancel debugging.
Huh? Why is VS 2010 coming up at all? I don't have it running. I'm not in it. I didn't press F5 in VS 2010. I am in VS 2008 and press Run/Debug there. What's going on; why is VS 2010 interferring?
Edit: Sorry I had to edit my answer. It turned out to be a little more complicated when two versions of VS are involved. Hopefully this edit is more accurate.
If you go to Tools > Options > Debugging > Just-in Time you can enable/disable JIT debugging for the specific version of VS. If you enable more than one VS as JIT debugger, you get to pick between them or set one of them as a default when the VS Jit Debugger is launched. I assume VS2010 replaced your VS2008 JIT debugger during install, so to re-enable it you need to launch VS2008 and go to the menu and enable it. I had to disable and then enable it to get it to work.
If you have set some other debugger, e.g. WinDbg as your JIT debugger, it is a matter of changing the following registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger to point to the desired debugger. Please note that if you run 64 bit Windows there's a shadow entry as well in the Wow64 section. This guide has additional details.