I have installed VS 2019 and UE4 v.4.11.0 but when I want to open a C++ project in UE4 I see that it can not recognize my VS2019 compiler.
How can I fix it?
Support for Visual Studio 2019 has been added to Unreal Engine 4.22: Release Notes.
After updating to Unreal Engine 4.22 or newer, ensure that you have set the Source Code Editor to Visual Studio 2019 in the Editor Preferences.
Additionally, if you have created your project with an earlier version of Visual Studio, you have to regenerate your project files: right click your .uproject file and click Generate Visual Studio project files.
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.
I do have a TFS Project (TFS 2013) and I would like to set up my Visual Studio 2015 to work at that project. I have Visual Studio 2017 and Visual Studio 2015 installed. Now whenever I go to the main page of my Project and click "Open in Visual Studio" (like described here), Visual Studio 2017 opens. I would like to have it open in VSTO 2015. How can I select which version of Visual Studio should open?
The solution file should contain a UTF-8 signature that describes in which version the solution is to be opened. This is what's used for example to show different icons for solution files targeting different Visual Studio versions.
This signature info is also used by the Visual Studio Version Selector when opening a solution. An easy way to fix this is make sure that have the solution local on your dev machine and then right click -> open with and choose the Visual Studio Version Selector. Then pick the correct version of Visual Studio that you want to use.
This will then be honored by your browser when opening a solution since this also uses the Visual Studio Version Selector.
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
Goal:
I try to open a visual studio project (c#) with CLR code for SQL Server from the Pluralsight course.
Issue:
I get no error messages just warnings below after One-way upgrade on Visual Studio 2017.
Your project is targeting .NET Framework 2.0 or 3.0. If your project
uses assemblies requiring a newer .NET Framework, your project will
fail to build. You can change the .NET Framework version by clicking
Properties on the project menu and then selecting a new version in the
'.NET Framework' dropdown box. (In Visual Basic, this is located on
the Compile tab by clicking the 'Advanced Compiler Options...'
button.)
When I open a solution with single project inside I get message below
The Project Needs to be migrated
or
The Project Needs to be loaded
Tried:
I tried editing csproj files with newer/older version numbers.
I tried different PCs with Visual Studio 2017 and Visual Studio 2015
Idea: Install Visual Studio 2010 as course was released in 2010 BUT I really do not want that.
When I got this issue, I tried reloading the project and when I did, it told me that I did not have an SDK installed and then it offered to install the SDK. Once I had the SDK installed, the project loaded and I was able to work with the 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