I has just installed Microsoft Visual Studio 2022. But I can not create file in project, as a result Start debugging is disable.
How can I debug code in this case.
Related
Context
I was able to debug my source generator in VS 2019 by setting the project properties/debug Launch to Roslyn Component, then the target project combo to one of my consuming project:
Now this feature seems to be missing in VS 2022, I can not create a launch profile using the Launch Profile UI with similar settings.
Question
How can I debug Roslyn source generator in Visual Studio 2022?
I got it working in VS 2022 17.1.0. Follow this instructions:
https://github.com/JoanComasFdz/dotnet-how-to-debug-source-generator-vs2022
Also make sure in the Visual Studio Installer that you have installed the .NET Compiler Platform SDK.
Visual studio crashes while building all.sln. I have all the source files. Chrome.exe is also working fine. But, It's been a week, I am not able to build chromium from Visual Studio. It shows this error message.
Unable to start program* allocator_clang_newlib_x64. The system can not find the file specified.
The all.sln is a very big solution with all the Chromium source code as Visual C++ projects. It will make Visual Studio slow even on high end machine. So the recommended way to debug your Chromium fork is via a standalone Visual Studio project. You can follow the steps below:
Open Visual Studio command prompt
Navigate to your Chromium's src folder from that CLI
Open Visual Studio to debug your Chromium executable by typing the following devenv /DEBUGEXE "out\YourBuildFolder\chrome.exe"
Press F5 to start debugging your source code.
Tip: If you want to start debugging by stopping at the entry point, on Solution Explorer pane, right click that project and choose Debug -> Step into new instance from the context menu.
You can use all.sln to edit the source code and yes you have to compile it again for the changes to take effect.
I have a project that is working correctly on Visual studio 2013 Ultimate.
Now we have installed Visual studio 2017 Enterprise.
When I compile and run my project on VS2017 , on several lines of code I receive a strange error message :
"Cannot obtain value of the local variable or argument because it is not
available at this instruction pointer, possibly because it has been optimized away."
What can I do , because on VS2013 I had no problems at all.
Thank you !
uncheck in the project "optimize code"
Also, set the debug info dropdown to full in the advanced options
go to Debug->Options or Tools->Options
and check Debugging->General->Suppress JIT optimization on module load (Managed only)
if you would like a technical reason, you need to post your code
I have a custom language and debug editor extension for Visual studio, that I'd like to be able to distribute using the visual studio integrated shell.
However, I am unable to open the custom project files using the integrated shell application:
Unsupported
This version of Visual Studio is unable to open the following projects. The project types may not be installed or this version of Visual Studio may not support them.
For more information on enabling these project types or otherwise migrating your assets, please see the details in the "Migration Report" displayed after clicking OK.
- scripts, "F:\path\to\example.myproj"
No changes required
These projects can be opened in Visual Studio 2015, Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1 without changing them.
- scripts, "F:\path\to\example.Example_sln"
Everything works fine when the extension is loaded as part of visual studio 2015 directly.
The custom project type was created using The Visual Studio Common Project System
Thanks to user rodya0 on Github, I have an answer:
Add the following:
$ShellFolder$\Common7\IDE\CommonExtensions\Microsoft\Project; \
to the PkgDefSearchPath section of the .pkgdef file in your isolated shell project
I am using Visual Studio 2013, but I'm in need to develop an old project using the Visual C++ 6.0 compiler.
For this purpose, I have been using Daffodil with no problem on Windows 8.1 for a while.
(You can read more how to use the VC++ 6 compiler in newer Visual Studio versions in this StackOverflow question: Is it possible to use the VC++ 6 compiler in Visual Studio 2012?)
Now I got a new Windows 10 machine, where I reinstalled Visual Studio 6, 2010, 2013 and Daffodil.
Using v60 build tools (Visual C++ 6.0 compiler), project gets compiled fine.
However, when I try to debug, VS says that "debugging information does not match", and I am unable to set breakpoints etc., but:
PDB file is there, same folder and name of debug executable;
Application built in Debug mode, with debug information enabled;
Debugger works fine when using Visual Studio 2010 or 2013 build tools;
Debugger works fine if opening the project inside Visual C++ 6 IDE.
I tried reinstalling all Visual Studio versions as well as Daffodil, but didn't solve.
Any clue what could the problem be?
Finally I actually found a working solution!
for VS 2013:
Enable "Native Edit and Continue"
under Tools->Options->Debugging->Edit and Continue
for VS 2015:
Enable "Use Native Compatibility Mode"
under Tools->Options->Debugging->General