While I was debugging a program in Visual Studio 2010, a dialog box popped up and asked whether I wanted to open up the firewall because of a remote debugging request.
Does this mean a person has initiated this request?
Simple:
This means that you are trying to debug a Method which belongs to an assembly on another machine (Another PC / Server / Device / ...)
Remote Debugging in Visual Studio
http://msdn.microsoft.com/de-de/library/y7f5zaaa.aspx
Related
I own a Surface RT and I was programming in Visual Studio 2013.
I found the tutorial online on how to set it up but I couldn't do it. Right by the part Visual Studio tries to find remote connections it doesn't find the surface. If I reboot the surface, right about when I open the remote debugger there is a small (10 seconds) period where it becomes available on my Visual Studio to select but it disappears right after never giving me the change to remote debug the app.
Does anyone had this problem before?
You can try adding the Surface's address manually.
Right-click your Windows 8 project, select Properties, go to Debug tab. Here select Target device: Remote Machine and then in Remote machin field enter the address and port your Surface shows you when you run the Remote Debugging Monitor (in the very first message you will see something like Msvsmon started a new server named 'SOMEADDRESS:PORT'. Waiting for new connections.). This usually helps when Visual Studio fails to find the device on it's own.
I have a classic ASP website deployed over IIS.
I am opening that website from the same location in visual studio 2010 (in order to debug, as per the steps mentioned here
The problem is that, when I hit F5 in visual studio it is giving me an error saying "your server does not support debugging of asp net or atl..."
I am able to browse the site from IIS, but I want to open it in Visual Studio in order to debug it.
What could be the possible reason and solution of this issue?
F5 doesn't do anything good for classic ASP sites (f5 will try to compile a .NET site and then access it).
I will assume that you are trying to debug the site on the same machine where it's running. The way you debug "classic" ASP using Visual Studio.NET is by attaching to the process running the site. The easiest way to do this is to use the Just In Time (JIT) feature: insert a stop statement in the code (debugger in jscript) - hitting that line should initiate a server-side "Error of type "Script Debugging" was encountered. Do you want to debug?" dialog, with suggestions of available debuggers to use.
Try this and report what happens - there might be some extra steps needed to configure that machine.
Are you using IIS 7?
If so you should the server option "Enable server side debugging"... It should be in the properties window of the site, using IIS Management Console.
Once you do that, when you run the server through Visual Studio, it should open another solution on debugging mode with the relevant code.
I have installed the Visual Studio 2010 Remote Debugger on a Windows Server 2003 (x86) server, and am attempting to connect to it results in the following error:
Unable to connect to the Microsoft
Visual Studio Remote Debugging Monitor
named 'ServerName'. The Visual Studio
Remote Debugger on the target computer
cannot connect back to this computer.
A firewall may be preventing
communication via DCOM to the local
computer. Please see Help for
assistance.
I have checked my Windows firewall setting, and ensured file sharing is enabled on my local machine. I have ensured that DCOM is running on the server, as well as the debugging service. There are no actual firewalls involved that I know of.
What else do I need to change to get this to work?
I just ran into connectivity issue. The problem was the Client PC (my desktop) could connect to Remote Host running debug monitor, but the Remote Host could not send data back to my desktop.
Turns out that it was caused by the 'Profile' setup in Windows Firewall. The Firewall rule was being limited to 'Public' profile - but my desktop was connected to the local domain. Changing the setting to 'Domain' ensured the Remote Host could communicate debugging data back to Client desktop.
Check under Windows Firewall -> Inbound Rules -> Microsoft Visual Studio -> Advanced Tab.
Cheers,
J
Here are the steps I took to get remote debugging to work against an ASP.NET app. Not sure if you've done this already, hopefully something might help.
On my machine (call it DEVMACHINE from now on) I shared out the folder that contained the remote debugger (msvsmon.exe). On my machine, it was located at C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\Remote Debugger\x86. I called the share msvsmon
On the server, I opened Windows explorer and navigated to \\DEVMACHINE\msvsmon, and ran msvsmon.exe (This opened the Visual Studio Remote Debugging Monitor)
On DEVMACHINE, I started Visual Studio 2010 and opened the solution that represents the application I'm attempting to debug.
In Visual Studio, clicked Tools > Attach To Process...
Entered the server name in the Qualifier field, then double clicked on the w3p.exe process that was in the list.
I then placed a break point in the location I wanted to start debugging
Couple things to note: The code deployed to the server was a Debug Build, the pdb files were there, along with the binaries. I had full admin rights on the server. No tools were installed on the server, I simply ran the exe that was located on DEVMACHINE. I did not have any firewalls between the DEVMACHINE and the server. And, both DEVMACHINE and the server are on the same domain.
Hope that helps.
I kept getting the same error listed above, and after trying all of the other answers, the problem turned out to be that DCOM was disabled on my development machine. The problem was solved by enabling DCOM using the instructions from this technet link.
I am using local DNS so I can test websites before they go live (by editing my hosts file).
I have a specific IP assigned by my router at home and at work.
i.e. dev.example.com is mapped to 192.168.1.123
When my machine changed to a different network without me realizing it could no longer reach the debugger and so I got the error.
Pretty obscure situation I had to get this error, which no amount of rebooting or recycling IIS will fix.
I had the same problems with the debugging service. The debugging service was starting automatically but I could never connect. I even turned off the firewall completely and that didn't help either.
Try running the debugging monitor (as opposed to the service) and connecting to that. You can find it in the start menu.
Confused about the difference between the monitor and the service? So was I. See http://social.msdn.microsoft.com/Forums/en/vsdebug/thread/afc80afc-c8eb-4831-915a-1edb8d188f98
Same problem here. My reason was that Trend security was enabled in the local computer, and it was blocking the firewall. I could not stop it because I needed a password, so I just deleted all the Trend processes, and it seemed to work fine. So you could check if some antivirus is enabled that is blocking the access.
I also needed to add devenv.exe to the Allowed Programs in the Windows Firewall in the local computer, and set its policies.
Below is a quick step to set up Visual Studio Remote Debugging Monitor on Visual Studio IDE.
Open Programs > Microsoft Visual Studio 2010 > Visual Studio Tools > Visual Studio 2010 Remote Debugger Folder.
A Windows Explorer shows the 32 and 64-bit versions of the Remote Debugging Monitor.
Copy the respective ver that matches remote server (e.g. x64 machine use X64 folder & x32 machine use X86 folder) to a folder on
your machine.
While at the console on your remote machine, go to the folder and start msvsmon.exe.
Go to Tools > Options and change the Authentication mode to No Authentication and check the box Allow any user to debug.
From your development machine, on Visual Studio, go to Tools > Attach to Process.
Change the Transport to Remote and the Qualifier to the name of your remote server.
You should now see the executable, which you want to debug on that list. Select the process you want to debug and click Attach.
You may now debug the code while it is running on the remote server.
Just remember to turn off Remote Debugging Monitor at the remote server once done.
Please refer below MS link:
https://learn.microsoft.com/en-us/visualstudio/debugger/remote-debugging-cpp?view=vs-2017
I have built an outlook addin, and I'd like to remote debug it running inside a vm on my dev machine (the vm is xpsp3 x32 and outlook 2010, my dev machine is 7 x64 with outlook 2007)
I have (after quite a bit of messing about with user accounts etc) got remote debugging working between vs2010 and the virtual box vm. I can attach to a simple test application and set breakpoints, and they get hit.
However, I can't seem to do the same with the outlook addin. I can't just attach to the outlook.exe process running on the machine as that does not seem to load the addin modules so the breakpoints never get hit.
I can't figure out how to get VS2010 to start outlook on the remote machine from a locally built project, I tried to follow these msdn docs but the instructions to set the working directory don't seem to work, so if I set it as the example suggests and start debugging it comes up with a message saying that the folder does not exist.
If instead I set the Start Action in the debug properties for the outlook addin project to 'Start External Program' and point it at the outlook exe, then VS2010 will successfully start the app, however, the breakpoints are not hit, even though it seems to indicate that they have been successfully set.
Has anyone been successful in remote debugging vsto addins? What am I doing wrong?
I know this is quite an old question, but just in case someone comes across this post, here is a solution:
On the host machine, in the VSTO project, add this at the top of the startup method.
MessageBox.Show("Debug");
Deploy the add in to the remote machine, open Outlook and the MessageBox should display
Run the Visual Studio Remote Debugging Monitor on the remote machine
On the host machine, set a breakpoint on the line after the MessageBox
In Visual Studio, select Debug/Attach to Process from the menu and attach to the Outlook process running on the remote machine
On the remote machine, click on the OK button on the MessageBox you added in step 1
The breakpoint you set in step 5 will now be hit
I have read this question and this page linked to in the question, as well as dozens of other articles about debugging asp classic with VS but it's still not clicking for me.
I am using VS 2010. The files I want to debug live on a remote server. I have installed the Remote Debugger on the server. I opened the website and attached to the w3wp.exe process on the remote machine. I created some breakpoints but I am still getting "The breakpoint will not currently be hit. No symbols have been loaded for this document" on those breakpoints. Is that the problem or is that a symptom of a larger problem with what I am doing?
First, by default, when you open a web site in Visual Studio, you're opening it via the file system, not via IIS. If this is the case, then Visual Studio uses the internal Cassini web server, rather than IIS.
The Cassini web server does NOT run classic ASP. IIS does. So the first thing you need to do is figure out how to debug in IIS.
It should go without saying, you need to have IIS installed on the machine you're working with, and have the web site you're debugging set up the same as it would be on the server. (so you should be able to run http://localhost/somepath and be able to see your site)
You also need to attach to the running process of Internet Explorer. There's a link to that as well.
Next, you need to get Visual Studio to attach to IIS and execute the web site rather than use the built-in web server and enable debugging.
That's covered here: This topic is no longer available (which is the first child link of the page you liked to in your question here.
From there, you should be able to follow the remaining links and get up and running.
Edit - added
This article takes you through it step-by-step.
Debugging Classic ASP ( VBScript ) in Visual Studio 2008
I've just had this problem when trying to debug a classic ASP application in VS2012.
There's no need to copy PDB files, because there aren't in this kind of projects, so follow this steps:
Be sure that ASP compatibility is turned ON in your IIS installation (Control Panel -> Enable/Disable Windows features -> Internet Information Server). You can install all features if you want to be sure.
Access to the IIS administration.
Locate your WebSite, then access the ASP configuration.
Find "Debugging properties" and then enable client and server debugging. You can also enable error sending to the browser.
After that, just attach the VS2012 debugger to the "w3wp.exe" process. DEBUG -> Attach to process....
This will work for local debugging. If you want to do remote debugging, you must prepare the remote server to allow remote debugging (TIP: Use the same user in both, server and your machine, and be sure it has enough privileges). For more information take a look at:
Installing the Remote Tools
Debugging Classic ASP ( VBScript ) in Visual Studio 2008