Installed Visual Studio Remote Debugger 2017 on Windows Server 2012.
Running Visual Studio 2017 on my laptop, I attached my code successfully to a process running on the server SOMESERVER:4022.
I run the target process on the server up to where my breakpoint should hit.
Visual Studio pushes to the front as if my breakpoint is about to hit.
I get "The network connection to SOMESERVER:4023 has been lost. Debugging will be aborted.
Notice that I connect using port 4022 but the connection loss notes 4023. I assume it's because I'm running x86 application on x64 server.
Ideas?
Related
I have question how to enable remote debugging in visual 2022
in my machine this feature is enabled till 2019 but now for 2022
wanted to understand what all packages needed for 2022 as existing packages already added to ( C:\Program Files (x86)) with my current project name
When execute some operation in one machine and trying to connect it with another machine with its IP addresses then connection should get establish and the remote debugging should be possible in another machine when we debugging with out installing Visual studio 2022 in different machine
I created a clean Web API .NET Core project and published it, using the default settings, to an Azure App Service, also created using all the defaults. Then I started up Visual Studio 2017 in Administrator mode and tried to attach the debugger. I got:
Unable to find a process called dotnet with arguments
.\MyCompany.WebApi.dll. The process may still be
starting, please try again.
What is wrong? Has anyone successfully debugged a App Service with .Net Core remotely. Seems like kind of a limitation of the environment if not.
EDIT: I upgraded to Visual Studio 2019 and was able to remotely debug processes running in Azure. There seems to be a critical failure with 2017 and Microsoft can't support it.
I deployed my MVC project to IIS and now I need to debug code by attach process but it not work.
These are steps that I did to debug:
Run my solution with Visual Studio Pro 2017 as Admin
Debug -> Attach to process...
Attach w3wp.exe process
Restart my site in IIS Manager
Run my site in browsers to debug
After above steps, my breakpoints always warning:
The breakpoint will not current be hit. No symbols have been loaded
for this document.
I can debug my code in the other PC with above steps but this way have problem with my laptop.
How can I fix this?
Thanks all.
I resolved my problem by:
Debug -> Options...
Uncheck at "Enable Just My Code"
I installed the newest Visual Studio Professional 2017 (15.8.5) to my laptop. In this version, above option is checked as default.
I can't Debug using a physical device in visual studio. It tells failure with an exception when I try to use my phone. my device debugging is enabled. When i build the in the browser simulator it works just fine.
Here is a pic of some of the error list errors.
I have set up a CI server for our .NET projects. To build those projects I want to use the Visual Studio executable devenv.exe.
This worked out perfectly during the "evaluation period". Now these 30 days are over, to keep using Visual Studio on my Desktop computer, I just updated my license with one mouseclick. Doing this on the server allows me to build using the GUI, but when running devenv.exe programatically with the required parameters, I am receiving an error that the evaluation license expired, even though I renewed it.
I have already tried a clean reinstall, which did not fix the issue for me. Visual Studio on the server is connected to the same account I am successfully using on my Desktop PC.
Is there a known fix for this issue?
Figured it out. The license is somehow related to the user that launches Visual Studio. So to to automatically build projects with devenv.exe, the building agent has to run under the same user account, that installed an launched Visual Studio.