I recently upgrade my VS2017 from RC3 to RC4.
Previously under the "Debug" section, when i launch as project there isnt Web Server Settings , however in RC4 its a required field. ( Refer to attached screenshot )
Also , previously when i run the project there will be a console popup where it shows all the output from "Debug" however in RC4 this console is also missing , is there any configuration or setting i should set?
Not avaliable
You can bring it out from the Debug Menu: Linux Console.
Related
I am trying to set up the Elrond VS Code extention in my mac. After installing the extension from the extensions tab, as instructed to set up a Elrond project I entered cmd+shift+p and click on Elrond setup workspace. After clicking yes to multiple allow requests I am getting the following error:
How can this be resolved?
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.
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.
Today I suddenly started getting errors when I try to run/debug my Azure cloud project from Visual Studio. I'm running Visual Studio version 15.7.3 and Azure SDK version 2.9.6. The error message says:
Failed to debug the Microsoft Azure Cloud Service project. The output
directory '\csx\Debug' does not exist.
Yesterday it worked fine, but during the night Windows Update installed some updates and rebooted my machine.
I have tried the following things without success:
Created the folder myself
Set full permissions for everyone on the csx folder
Set full permissions for everyone on the parent folder to the csx folder
Uninstalled one of the updates which was installed during the night
The strange thing is that if msbuild creates the csx folder without problems, using this command:
C:\src\services2>msbuild <cloudproject>.ccproj /p:configuration=debug /maxcpucount /p:outdir="c:\OutDir" /p:overwritereadonlyfiles=true /p:targetprofile="Cloud" /target:Clean;Publish
Any suggestions on how to fix this problem?
After struggling with this problem for a long time, I concluded that it was a problem with Visual Studio, since msbuild worked without problems.
After running a "Repair" on Visual Studio, it now works again :-)
You run the repair by selecting Visual Studio from Settings/Apps & features and clicking "Modify":
In the Visual Studio installer, you then select "Repair":
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.