I am trying to setup remote debugging to one of my webservers. I have installed Remote Debugger and configured it to my user name on the web server. When I attempt to attach to process in VS 2012, I am able to connect (Remote Debugger on the server shows the log), but when I go to the web site url, my breakpoints are not being hit. Has anyone else had this issue?
Related
I had a Windows 2008 Server which was being used as Application server that has recently been upgraded to Windows 2012 -> Windows Server 2016 -> Windows Server 2019.
All of the applications under IIS work, but one. I am trying to figure out what is wrong. I have installed Visual Studio 2019 Remote Debugging tool on the server and trying to attach to the erroneous project under IIS.
I have the Remote Debugger running
but when I try to attach to remote process the Application pool and user names do not show up in the "Attach to process" window.
Since I can not see the details I can not connect to my application and debug. I am sure that "Show processes from all users" is checked.
I know that if the application does not run on the server it does not show up in this list, but I have called other applications under the site which are running but they don't appear either.
Try run the remote debugger under the different user account:
You can stop the remote debugger and restart it with the account you are using on the local computer.
You can start the remote debugger from the command line with the /allow parameter: msvsmon /allow username#computer
You can add the user to the remote debugger's permissions (in the
remote debugger window, Tools > Permissions).
If you can't use the methods in the preceding steps, you can allow
any user to do remote debugging. In the remote debugger window, go to
the Tools > Options dialog. When you select No Authentication, you
can then check Allow any user to debug. However, you should use this
option only if you have no choice, or if you are on a private
network.
I want to use the remote debugger for VS2017.
But every time I started it on my VS machine I got the following error message:
"Could not launch debugger. Check the Debug settings.."
Do you have any hint, where can I get more information about the problem, like remote debgger not started, Proxy problem, settings... ?
Or how I can fix it ?
I setup the remote debugging connection for VS2017 on two Windows 10 machines.
On the remote debugging machine I started the tool by execution of msvmon.exe (by sharing the folder location on the machine, on which VS2017 is running).
It seems to run without any error, since a window was open with displays the machine name and the Port.
I copied then this information in the Remote Server Name field for the Visual studio debugger. I tried it with and without port number).
I also copied the debugger application to the same folder of the remote debugging machine, as it is on the VS machine.
After that I started the Remote Debugging session and the error message is shown.
Thank you very much!!
I could solve the issue. The problem was that the remote command parameter was not set. :-(
I am using the Azure Mobile App quickstart ToDoList example to get started with cross platform app. I have set up the back-end and it is working on localhost - I can hit it using Swagger and gets posts etc are working.
I then set up the client application (Xamarin.Forms). I am running the client application on my Android device and all works great when back-end is in Azure, including the offline sync element. The problem is that I have to work locally for now but I cannot sync with the db when running on localhost.
At first the debugger was giving me a "connection refused" error, so I followed the steps here and in various other sources including using my laptop IP and setting firewall rule, adding binding to port in IIS Manager and applicationhost.config, and changing ApplicationURL in Constants.cs.
Now, I get no connection refused error, but the data is not getting to the db, athough the localdb on the tablet seems to be working - it is failing when I try to sync to/from db.
Not too familiar with networking but it may be important to note that when I use localhost:portnum/tables/todoitem in browser I get results in XML but when I use 192.168.0.10:portnum/tables/todoitem I get "Bad Request - Invalid Hostname".
By default, your Mobile App .NET server backend application will run in IIS Express. This is problematic when debugging with a client application running in another device on your network, or in a virtual machine in Hyper-V (such as Windows Phone Emulator). IIS Express will host your server application under localhost, which makes the application unreachable to other devices or virtual machines. Your client application running on Windows Phone Emulator has a different meaning for localhost. The same is true for the Visual Studio Emulator (which runs in Hyper-V) and the Google Emulator.
It is simpler to configure your machine to host your Mobile App .NET server backend application on IIS, as this allows you to control the binding of the server application to an IP address, rather than localhost.
For information on this, see: https://github.com/Azure/azure-mobile-apps-net-server/wiki/Local-development-and-debugging-the-Mobile-App-.NET-server-backend
I have an MVC core website written in C# which is deployed to an AWS EC2 Instance with Windows Server 2012 R2 and IIS8 deployed on it.
I am trying to remote debug the application as I am getting errors thrown which I don't when running locally (details for another post maybe).
On AWS Console, I have a security group with the following Rules as guided by here:
and when I click on Debug->Attach to process, and browse to my AWS instance, I can see the correct dnx.exe process, however, when I attach to that process,
I get the The breakpoint will not currently be hit. No symbols have been loaded for this document
I've tried going to Tools->Options->Debugging->Symbols and clicking Load all symbols as it is my understanding that since VS2012 the symbols do not need to be deployed, but rather just on the local machine doing the debugging, taken from here.
In versions of Visual Studio before VS 2012, debugging managed code on a remote device required that the symbol files were also located on the remote machine. This is no longer the case. All symbol files must be located on the local machine or in a location specified in the Debugging / Symbols page of the Visual Studio Options dialog box. See .NET Remote Symbol Loading Changes in Visual Studio 2012 and 2013 on the Microsoft Application Lifecycle blog.
I can see the connections being initiated in the MSVSMON process on the EC2 instance.
I feel like I'm close but I'm just missing one simple thing.
You need to check on which port the Remote Debugger is running and allow inbound traffic on that port by opening Inbound Port [4024 in my case] with a Custom TCP Rule for Remote Debugging.
You can check the port used by Remote Debugger at Tools > Options in the Remote Debugger Menu.
Hi I have a IIS server (running on Windows Server 2012 R2), I installed VS2012 remote debugger on it and configure the VS remote debugger run as a service. By default I have debug permission to this IIS server.
Now I want to give another colleague remote debugging permission to my server, but after I spent few hours, I still don't know how to do.
Because msvsmon.exe is run as service, it doesn't have UI, how to add another domain joined user?
I tried to configure msvsmon.exe run as application, and I added my colleague through its UI, however, after I close msvsmon and restart it, new added user is gone from permission list.
Can someone help me on this?
Run cmd (Command line) and add the user to the remote desktop users
net localgroup "Remote Desktop Users" domainname\username /add
If that fails, run command line as administrator and run the command again