I am suddenly unable to debug in VS. I am developing an MVC app. I made no changes whatsoever to application settings. I simply modified a property in a class like I've done many of times.
I am getting the popup
Debugging Not Enabled
This page cannot be run in debug mode because debugging is not enabled in the Web.config file. What would you like to do?
(.)Modify the Web.config file to enable debugging.
( )Run without debugging.
I have compilation debug="true" targetFramework="4.0" in my Web.Config file. Clearly debugging is enabled. I've restarted VS, rebooted, but same thing.
When I say immediately, I mean from one debug session, to another within about 10 minutes. Any ideas why this is happening?
Copying somebody else's fix to your question, see if that helps:
Fixed this by registering/installing ASP.NET 4.0
c:\windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i
If you're using 32 bit change Framework64 to Framework.
Link is Unable to start debugging on the web server
Try see if it works
Related
I have an ASP.NET Core application which was running fine but while developing (and after the Windows 10 April update, most likely just a coincidence) suddenly, I got two messages:
This file does not have an app associated with it for performing this action. Please install an app or, if one is already installed,
create an association in the Default Apps Settings page.
Unable to start program 'programName' Invalid pointer
Result: I cannot debug/ run my application anymore. (Start Debugging/ Start Without Debugging)
I found some scary search results talking about a corrupt file system but I don't think that it is something like that in my case...
I checked my startup projects, restarted Visual Studio, restarted the whole system... nothing helped.
Update: After installing the latest Visual Studio update (15.7.1), the message I get when I activate the JavaScript debugging again has changed. Now it states:
Cannot connect to runtime process, timeout after 10000 ms - (reason:
Cannot connect to the target: connect ECONNREFUSED 123.0.0.0.1:53232)
Result: Still the same. Only the error message changed.
Any hints, ideas about that one? Thank you!
If not an answer at least a workaround. I can work again if I tweak the debug options
Debug -> Options -> General -> Enable JavaScript debugging for ASP.NET
(Chrome and IE)
If I disable this feature, I can debug and run my application again. But I still don't understand why this is happening now nor how to use JavaScript debugging now...
I had this problem with Visual Studio 2017. It was caused by my antivirus (bitdefender) blocking a chrome temp file. I set it to ignore that file and that fixed my debug issues.
The file was C:\Users\[username]\AppData\Local\Temp\vschrome_diag.lnk
According to this, re-installing chrome may fix the problem.
Error launching vschrome_diag when Visual Studio 2017 starts debug on Chrome
I'm trying to debug an old asp web site on a windows server.
actualy I don't have any project files (there is no visual studio project file), what I have is only web pages in a directory ... I can run this latter on a IIS6 and everything works fine, the problem is that when I try to run those pages in a debugging mode nothing happens!
I enbabled the debugging mode on the IIS and I attached this latter's process to the visual studio (I'm using VS2005) I set the breack points... but nothing happens even if I ran those pages code the compile doesn't stop!!
I saw several pages talking about this topic... but I wasn't able to find a solution... do you have any idea?
(I want to add that the web pages, the IIS and the Visual studio ide are on the same server and I'm connected with the administrator session)
Make sure you when attach to set it to attach to Script code only and the break points must be within server-side code.
Given a working Internet application written in classic ASP (with some VBScript) and an IIS 8.
Now I have to debug that application probably in VS2012 or VS2010.
I hear about some rumors, that I can configure the IIS to do that.
Furthermore when I write STOP keyword to the code file (in text editor) then the visual Studio will be triggered to attaching the actual debugger.
Please help me with these IIS or other settings, and ask if the situation is unclear.
What are tried:
in your iis in the asp section set under debug properties "serverside debugging" to "true".
I had to attach to the IIS working process w3wp.exe in Visual Studio manually. Somewhy that wasn't automatical but i saw cases on other computers when it was...
I have a solution where i have 8/9 projects.
everything was working good and suddenly, I started to get an error when I start to debug. and it says
Unable to start debugging.
If I close visual studio and run it again, it works in the first try.
and after that it stops working.
In the configuration manager it is set to "Any CPU".
I tried many thing with no luck. Is there any help??
this is how the error looks like..
I got similar error:
"Unable to start debugging. Check your debugger settings by opening
project properties and navigation to 'Configuration properties --> Debugging"
I have solved it by setting :
Properties--> Debugging --> Working Directory
to $(ProjectDir)
As it's an MVC web application, there's a couple of things to check. Firstly, are you sure the web project is set as your startup (this catches me and a couple of others in my office out from time to time)?
Secondly, where are you hosting the project? Are you using Cassini, or are you hosting it in IIS while you debug? If so, check IIS and make sure that the site is started, there's no issues with the AppPool, etc.
Finally, one way to try is to actually press Ctrl+F5 to run without the debugger attached, I often find that IE will then actually display an error that's causing the issue.
I have a web application that I've always been able to run in Visual Studio and it debugs just fine (breakpoints work, I can pause execution, etc). Recently, the behavior changed suddenly, and a few things happen:
I start debugging, it lauches IE and loads the application, but after a few seconds (sometimes the page hasn't even displayed yet), Visual Studio acts as if debugging has stopped - I'm able to edit code in VS again, and the "Play" button on the toolbar is enabled. The application continues to run in the IE window just spawned, but I'm not attached to it
During this few seconds that VS is "debugging", because it detaches, my breakpoints show as hollow - as if I'm set to "Release" mode and they won't be hit. In fact, I have a breakpoint set in Page_Load, and it skips right by. I've checked, and I'm set to debug mode, though the compile mode dropdown is missing from my toolbar (I checked in the build properties to ensure I was in debug mode).
Can anybody shed some light here?
It turns out that this was actually a result of an upgrade to Windows Vista. VS wasn't being "Run as an Administrator", which caused it to lack the rights to attach to other processes for debugging. As a result, debugging would stop right after it started. Changing the VS shortcut to run as an administrator resolved this problem.
I've experienced samely looking behavior. The cause was in existence of several <system.web> sections (which is allowed by web.config schema). Visual Studio debugger (versions 2008 and 2010 were tested) looks in the first encountered section only. So if your <compilation debug="true"> tag is not in the first one, it thinks that there are no compilation.debug setting present and genrally tryes to add <compilation debug="true"> to the first <system.web>. In some cases VS2008 just silently procceds in this case. For example look here: https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=510354#details"
Have you installed anything else on the server / workstation recently?
We have a third party app that doesn't allow us to debug, w3wp.exe crashes immediately upon an attempt to debug.
I ran into something similar when I had placed some code in a constructor that was crashing. Exact same issues where the Debug would disconnect just after the application started up.
The short if it, check that you haven't configured a class constructor to run during web startup that is crashing...
Quick windows 7 update: I had to add "localhost" to my list of trusted sites to correct this issue...go figure.
Just a workaround for those (like me) for whom the above solutions do not work: After starting the app you wish to debug, go to Debug -> Attach to Process, and attach it to the process you want to debug. Works on my machine.
In my case, I faced this issue with Visual Studio 2019 and 2022 as well.
I tried upgrading/downgrading Visual Studio versions but nothing helped.
On debugging, I finally found the root cause and sharing it here to help others facing the same problem.
I was using Brave browser with Visual Studio and whenever I uploaded a file in my application, the Visual Studio debugging stopped automatically. The root cause of this issue is the feature in Visual Studio to stop debugging on closing the browser. With Brave browser Visual Studio feels like we have closed the browser on uploading the file. So to fix this issue I have turned of this setting as given here.
You can find this setting here
Tools > Options > Projects and Solutions > Web Projects > Stop debugger when browser window is closed, close browser when debugging stops
Just turn it off and everything should work fine.