Can not debug with attach to process VS Pro 2017 - visual-studio-2017

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.

Related

Visual Studio 2017 Remote Debugging of Azure App Service Not Working

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.

'Starting LLDB server' when debugging c++ in Android studio

I want to debug c++ module in Android Studio.
I create a project with c++ support in android studio.
When i debug, this is what i get.
'Starting LLDB server' will never stop. If I stop debugging, its still there. If I exit android studio, i get warning about running background process. I already installed LLDB in SDK manager. I have enable debugging in my device.
What should I do?
In Android Studio 3.5 I encounter similar issue with LLDB debugger - where "Starting LLDB server" process hangs forever, no debugging process is started. Check this answer.
I was having this problem today all of a sudden Android Studio 3.5.3. What fixed it for me was to uninstall & reinstall Android SDK Platform Tools and LLDB.
This was the exact steps I followed:
Open Android Studio
-> Preferences
-> Appearance & Behavior
-> System Settings
-> Android SDK
-> SDK Tools tab
Uncheck LLDB and Android SDK Platform-Tools
Click Apply & let sdkmanager uninstall those items.
Re-Check LLDB (I'm using 3.1) and Android SDK Platform-Tools (I'm using 29.0.5)
Click Apply & let sdkmanager install those items
Quit Android Studio & any running emulators
Restart Android Studio
After that, running the debugger no longer hangs at Starting LLDB Server for me.
I was having the same problem. I realized it was caused by using ADB over WiFi.
But when I connected the phone via USB cable and tried to start debugging this way, it was still stuck.
I had to disable the WiFi on the phone and then it started working immediately.

Click Once application works when published from Visual Studio 2010 but not Visual Studio 2017

VS2017 publish causes error on startup "cannot load file or assembly ..." Running directly from the build works but not from the deployment in app.publish folder. The error shows even on my development computer. However, opening the same solution in VS2010 and publishing from there, all works as expected. I cannot find this same issue on the web.
After searching for all things Click Once, I came across an answer for a different issue and tried it. I upgraded the target framework to .NET Framework 4.6.1 and updated the NuGet Packages. Afterward, I was able to publish and run the Click Once Application with no errors.

Building Visual Studio project on Windows Server 2012

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.

remote debugging windows 8.1 driver Visual studio 2013

I'm trying to set up remote debugging on Visual studio 2013.
I think I installed everything on my computer and the hyper-v machine too + updated.
So whats happening:
I open a microsoft UMDF driver sample. (I can build it without any errors).
I select Debugging tools for windows remote debugger.
Then a message box pops up named Deployment not configured.
I select I know what I'm doing continue debugging.
Then the Computer configuration wizard starts add new computer.
I select provision computer and automatically configure debuggers.
Then the configuration process configure my hyper-v machine fine.
Installs the necessary files restart the computer and log in with the name WDKRemoteUser.
Then I Click Finish then this error pop-up.
The required property 'DbgengRemoteCommand' is missing or empty. (OK)
So I need to fill up the package property pages->configuration properties->debugging->
Remote Command, Remote Command Arguments, Remote Working Directory, Remote Computer name manually?
And if I had to what should I write there or I miss something else?
You only need to specify the "Remote Working Directory" parameter and you can just give it the same path as your build directory and you should be good.