I'm using Visual Studio 2015 to debug a website running on a .NET framework. When setting break points in one of my .aspx.vb files it gives me an error saying:
"The break point will not be hit. No symbols have been loaded for this document."
Now I have solved how to fix this error by going to Debug -> Attach to Process then attaching it to the process of my IIS.
The issue is I have to do this every time I stop and restart debug mode. Is there anyway to get this process to automatically attach when I begin debugging?
The ReAttach extension gives you an easy way to ReAttaching your prior debug targets.
Related
EDIT: Good information provided below to diagnose, but the issue was I was running Visual Studio 2022 17.3. Version 17.4 is required for .NET 7, and I had just installed that. Once I installed the latest version of VS, all my problems went away. Install with Visual Studio
Suddenly today, debugging my ASP.NET Core 6 and 7 apps suddenly has stopped working. I hit F5 to debug, it stops on my breakpoint, but as soon as I continue or step into, I'm shown this dialog:
I haven't made any changes to code, I'm simply trying to continue after I've stopped at a breakpoint. This just started happening today and I can't figure out what I did.
I haven't made any changes to code, I'm simply trying to continue
after I've stopped at a breakpoint. This just started happening today
and I can't figure out what I did.
Well, if your visual studio stop working for debugging all type of application, please check following configuration:
1. Tools > Options > Debugging > .NET/C++ Hot Reload
2. Tools > Options > Projects and Solutions > ASP.NET Core >
Furthermore, If you select the Always rebuild option in the dialog box, you won't see the dialog box again in the current Visual Studio session, and Visual Studio will automatically rebuild and reload instead of showing the dialog box.
Note:
In addition, as you can see above in the first release of Visual Studio (version 17.0) the standard Edit and Continue dialog is still shown when using Hot Reload with the debugger. This was a bug and has been resolved starting with 17.1 Preview 2 release.
If you still need more details about the issue you are having with, I would higly recommend you to check our official document here.
If issue still perist:
After checking above configuration, if your issue still persists and if you are not using Visual Studio (version 17.0) then you still reset your unknown setting in visual studio as following:
Go to Tools > Import and Export Settings.
Then No, just reset settings
Finally, restart Visual studio.
You can get more details here.
I have created a COM add-in for Excel.
I know that I can enter debug points into my code and then choose to "play" my code from Visual Studio. When a debug point is hit, execution stops and I enter debug mode.
But is it possible to create debug points that cause execution to stop and debug mode to start when I am not running my code via "play" in visual studio but just opening an Excel file as normal?
You can attach the debugger after you run Excel manually outside of Visual Studio. See Attach to Running Processes with the Visual Studio Debugger and How to: Attach to a Running Process for more information.
"Unable to start debugging 'C:\Windows\System32\WWAHost.exe'. The Microsoft Visual Studio Remote Debugging Monitor (MSVSMON.EXE) does not appear to be running on the remote computer. This may be because a firewall is preventing communication to the remote computer. Please see Help for assistance on configuring remote debugging."
Searched for similar posts, but didn't found one. If duplicate just inform.
I am not trying to connect to any remote machine. Just testing on my local machine.
Is there any way to solve this issue. (I'm using Windows 8 Enterprise 64-bit, just a javascript project)
Problem solved. Installed Remote tools update from here and working fine. Thanks for responding. Closing the topic.
I had the same problem. I fixed it by changing properties/compile/target platform to x86 instead of Any CPU. It solved the problem in my case. Hope it helps.
This happened to me just now when I had a website set up in IIS for mydomain.com, and set my project's start up url (Local IIS) to mydomain.com, and then launched the project before remembering to add a record in the host files for the domain:
127.0.0.1 mydomain.com
This got me for a good hour before I remembered I never set the record. Adding the record fixed it right away.
Windows 7 x64, VS 2012
In my case, the Remote Debugging Monitor component was installed and the app was clearly configured to debug locally in settings. This was a WinForms app upgraded from VS 2008, .NET 3.5.
Turns out it was the Windows Firewall. By directly running:
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Remote Debugger\x64\msvsmon.exe
A firewall dialog appeared where I could allow msvsmon.exe to run. After a VS 2012 re-start, debugging (locally) was fine!
Ensure you have Local Machine selected in this drop-down menu:
Windows 7 x64, VS 2012, VB.NET
I fixed it like this:-
Create a shortcut on your desktop to "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Remote Debugger\x64\msvsmon.exe".
Right-click shortcut and select "Properties" from the dropdown menu. Select the "Compatibity" tab, tick "Run this program as administrator" and click OK
Create a shortcut on your desktop to "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe".
Right-click shortcut and select "Properties" from the dropdown menu. Select the "Compatibity" tab, tick "Run this program as administrator" and click OK.
To start VS2012:-
Double-click the msvsmon shortcut icon (that you created above, to launch msvsmon). Wait for the "Visual Studio Remote Debugging Monitor (Administrator)" window to display before continuing ...
Double-click the "Visual Studio 2012 Professional" shortcut icon (that you created above, to launch VS2012)
In VS2012, ensure standard toolbar is visible.
In VS2012, ensure "Solution Platforms" dropdown (on standard toolbar) is visible and set to "x86".
and debug now works (for me anyway) ...
However after 15 minutes or so, debug may stop working and you may get the msvsmon error again. If that happens, simply close VS2012 and msvsmon and then start again (from "To start VS2012:-" above) ...
Myself and several other developers have been trying to look for a solution for this problem for about 3/4 hours as Visual Studio crashed then this error would occur (twice in 2 days). I then suddenly (after a lot of debugging and trying other suggestions and headbanging) I somehow realised that the file which was highlighted had changed and when I was trying to debug was not the MVC app project, once I changed it to my project's one it then worked.
Hope this helps and saves people from hours of pain!
I also got this error, I usually run sites under a named user (which is also a database user) and forgot to set the Application Pool. (parliament's answer also helped me)
For me this worked in VS2013:
Save your work, close Visual Studio then reopen your project
I encountered this error as well.
The cause of mine was that I had accidentally emptied out the following property
Properties->Debugging->WorkingDirectory
Changing it to:
inherit from parent or project defaults
Solved the issue.
If you are using Microsoft's Azure, try attaching manually the debugger:
I have outlined the steps in the following answer:
https://stackoverflow.com/a/35738995/1057052
I am compiling and running code at runtime. Can I stop this code midway through if I wish? Like the 'stop' feature in Visual Studio that stops the code if desired?
You can, if you attach the Visual Studio debugger to the running process.
Load the solution that produced the application into Visual Studio
Run your application outside of Visual Studio
Choose Debug -> Attach to process... from the Visual Studio menu
Select your application in the process list
Click Attach
You should now be able to use the normal debugging controls to pause execution of your application, step through code, etc.
Yes, it's called the task manager (find your process and kill it). Or if you're in a console window, just use Ctrl+C.
The question really says it all. For one project I am working on, the Visual Basic Compiler crashes resulting in me having to restart my IDE.
It looks like it crashes when copying a PDB file and XML file for the web site for obj/debug to the output folder.
Has anyone experienced similar crashes? If so how did you repair it?
Are there any crash logs stored anywhere??
I am using visual Studio version
8.0.50727.762 (SP .050727-7600)
After contincually hitting send error report to microsoft I finally got a little message box saying "We think this might be your problem" with this Link
I believe this is my problem... I have still to obtain the hot fix
Do you actually get an error message or code when it crashes, or do you just get the "Visual Studio stopped working" error message?
I'd second trying to uninstall, reinstall, and reapply SP1, just to make sure it isn't something with your installation. I've never had the VB compiler crash on me, and I'd imagine that permissions problems and other exceptions moving a file would be completely covered within the compiler's internals.
You can try using the event viewer in Administrative Tools to see if any logs were recorded.
Looks like you aren't running Visual Studio 2005 SP1. We had tons of VBC crashes before SP1 -- it was a wonder they even made to RTM on the product. Just terrible. Install Service Pack 1 and your problems will most likely go away.
Have you already tried cleaning your solution/project?
Sometimes the .suo, .ncb and other files maintained by Visual Studio get corrupted resulting in crashes during complilation or debugging.
Simply delete .SUO file and get Nirvana :)