I have local my projects asp.net open in visual studio 2010. And also copy this project to IIS folder in remote hosting. Cause in hosting directory I don't have VS so I copy there remote debugger application. I connect from my Visual Studio to IIS process on hosting, but any of breakpoints not fire.
Why ?
I had the same issue when I connected using the Transport in the "Attach to Process" dialog set to "Remote (native only with no authentication)". I was able to connect to the IIS process (w3wp.exe for IIS6 on Win2K3), but no breakpoints were hit when I navigated within the web app.
To get it working, I changed the Transport to "Default". Then I ran into numerous issues with successfully connecting to the Visual Studio Remote Debugging Monitor. But once I resolved them all and was able to get the list of processes from the remote machine, I could connect to W3WP.exe and voila, my breakpoints started working and I was able to debug normally.
You don't provide much detail on your local and remote configuration, so this just a guess whether it might help.
Related
I have recently deployed my ASP.NET Core application to my IIS8 server. However due to some issues, I have to remotely debug it.
I installed the Remote Debugger and managed to connect to the server and Attach a process.
However, I am unsure of what to attach from there. I have tried attaching all dotnet.exe and w3wp.exe processes but each time I do that, my breakpoint turns white and says that it won't hit.
I took a look at my Modules tab and for some reason, my symbols aren't loaded for my application dlls. I have made sure that the configuration is Debug and that the ASPNETCORE_ENVIRONMENT is Development.
Currently this is what I am doing:
Run the Remote debugger on the IIS server
Run the website on my local laptop
Attach a process in Visual Studio
I am using Microsoft Visual Studio Enterprise 2019 Preview on Windows 10 pro. My project (source code) is https://github.com/smartstoreag/SmartStoreNET/tree/3.x/src . I press F5 to see result, but I catch error
Unable to start debugging on the web server. The Visual Studio 2019
Remote Debugger (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.
How to fix it?
You may need to set up the website in IIS, and possibly add an entry to C:\Windows\System32\drivers\etc\hosts.
Check the project properties to see what URL needs to be set up.
Alternatively, you could try running in IIS Express instead of IIS.
In my case the related site(s) in IIS tied to my solution were "stopped" in IIS. Once I went into IIS and "started" them, this debug error went away.
We have some released ASP.NET project and now we are supporting it. I installed Windows 8.1 on my macMini and cloned that project. The webSite works on server normally and locally on machines of other developers. IIS configured as well. When i trying to browse webSite from IIS manager I have the following problem in chrome:
This webpage is not available
ERR_NAME_NOT_RESOLVED
When i try to debug via Visual Studio by pressing the debug button i have this:
Unable to start debugging on the web server. The debugger cannot
connect to the remote computer. The debugger was unable to resolve the
specified computer name.
But i think it's ok, cause we are debugging this project pressing Ctrl+Alt+P and attaching to w3wp.exe process, but it's not launched. Actually this should be launched automatically, as i know.
Windows 8.1; MSVS 2015; .NET 4.5.1;
I tried to restart IIS. And i configured binding to my website with host name myWebsiteName and port 80.
Update 11.6.2015 :
And one more thing! The default web site works fine.
Are you running as Administrator? Also try these commands:
ipconfig /flushdns
ipconfig /renew
ipconfig /registerdns
from the command-line (running as Administrator)
I'm trying to debug an ASP.NET application for my company internal portal on a remote IIS v7 server running on a Win 2008R2 server. The IIS server is on the same LAN as my development workstation.
The portal mostly works, however there is one function that doesn't work correctly when published to the remote server.
If I debug the application locally, using either the Visual Studio Development server or the local IISExpress server, the function works as expected, so it seems that I need to debug from the remote IIS server.
I have installed the Visual Studio 2010 Remote Debugger (msvsmon.exe, x64) on the remote server and have published my web app there. I'm running msvsmon on the remote server as an administrator.
On my local Win7 development machine, I have the portal solution open in VS 2010 from my local hard drive, I can connect to the Remote Debugger from Visual Studio using the Tools | Attach to Process menu and I have selected the w3wp.exe at the process to attach. The msvsmon app on the remote server shows that I have connected.
Back in Visual Studio on my local machine, I set a breakpoint on a Page_Load method (where I suspect my problem code is), however, my debug options to Start, Continue, Step Into, Step Over, etc are all disabled.
I'm apparently missing some step or concept here, but I'm at a loss as to what it is.
We have a Windows Server 2008 R2 box setup as a Terminal Server with Visual Studio 2012 installed on it for remote developers to be able to do development on our ASP.net systems.
We would like to be able to do debugging on out projects the same way we do when developing on our local machines using visual studios internal development server.
I am trying to start local debugging on an ASP.Net project (F5) in VS2012 - the project compiles - IE comes up with my localhost url and then it just spins with "connecting..." and the page never comes up.
Pulling up the same workspace on a local machine and debugging comes up just fine.
I've exhausted my google-fu on looking for solutions here and humbly ask you all for any insight.
Visual Studio works a little differently when you are debugging on a server. You don't really want to use VStudio to play/debug on a web server. You need to use the menu option "Debug", "Attach to process". There will be several processes running, so it might take a few tries to find the right process.
Be careful though. Because your break-points will actually freeze IIS for the entire server. It could be a pretty big inconvenience for everyone who is using IIS at the time.
If you are trying to debug the project from your IIS server, you need to verify if the account has Administrator rights, also if the project has been deployed with its source files, you can attach the process (maybe it is w3wp.exe) in Visual Studio and debug it.
Another way is to open the solution using Visual Studio and change in the web project's property the server: Use Visual Studio Development Server.
Let me know more info about your scenario to provide you more paths.
What I would do is attach to the IIS process on the server: http://msdn.microsoft.com/en-us/library/vstudio/3s68z0b3.aspx you can even do this off your machine.
make sure debug is enabled in web.config for that app and you've mounted the remote project. Add a break point, debug by attaching to the IIS app pool process & it'll trigger the break point.
I was able to Attach Process to the SPUCWorkerProcess.exe even though it's a farm solution and not a sandbox solution