The new POCO library version 1.12.1 NET project does not compile in Visual Studio 2022, it does not even load the project. I had to set the Visual Studio version in the project properties from 2019 to 2022 simply to be able to open it. But it does not compile!
Eduardo Quintana
Related
Using the latest Visual Studio 2019 version, a brand new project will not build:
fatal error LNK1104: cannot open file 'MSCOREE.lib'
I have tried to re-install Visual Studio but that didn't change anything unfortunately.
These components have been selected by the installer but apparently it's not enough:
MSVC v142 - VS 2019 C++ x64/x86 build tools (v14.24)
Windows 10 SDK (10.0.18362.0)
C++/CLI support for v142 build tools (14.24)
Question:
Are there any tricks to get CLR Class Library (.NET Framework) projects to build ?
Here is the solution:
Apparently, no matter what framework version you will target, the $(NETFXKitsDir)Lib\um\x86 macro will always point to C:\Program Files (x86)\Windows Kits\NETFXSDK\4.7.2\lib\um\x86.
Now here's the problem, even though you install 4.7.2 SDK in Visual Studio Installer, this file is nowhere to be seen.
But if you download .NET Framework 4.7.2 Developer Pack Offline Installer and press the Repair button, it gets correctly installed and a brand new project will build succesfully.
Alternatively:
Re-installing VS also fixes the issue ...
I have installed the community Visual Studio 2019 version 16.4.
and clone the solution of .NET Core 3.0 but no project loaded something wrong in the SDK.
I have installed the SDK and runtime for 3.0 and 3.1, but still can not load any project.
You could fix the VS 2019 issue with the below steps
Run dotnet --list-sdks to know the exact version of the SDK installed
Modify the global.json file in the root folder of the project (For example,the project was showing 3.0.100 but you had 3.0.101 installed, you need to edit the same to point to that version and you could be able to reload the projects.
References:
https://learn.microsoft.com/en-us/dotnet/core/versions/selection#the-sdk-uses-the-latest-installed-version
https://learn.microsoft.com/en-us/dotnet/core/tools/global-json#globaljson-and-the-net-core-cli
I had the same problem after I uninstalled Visual Studio 2022 Preview. Removing the C:\Program Files (x86)\dotnet\ directory from my PATH variable solved it.
I'm migrating a C++/CLI project from VS2008 to VS2017 but I always get an error when "reloading" the project to convert.
The project don't load and I don't see any clear error message about the reason.
You should check that the correct components of Visual Studio 2017 are installed.
May be it's not installed by default in your case. It happened to me when I installed Visual Studio 2017 using this chocolatey package
You can solve this issue with the steps in this question: Visual Studio 2017 Professional C++/CLI Missing
Now that ASP.NET Core is shipped with VS 2017(getting released on March), How long will they support ASP.NET Core in VS 2015?
I mean project.json will no longer be used, then do we need to move existing projects to VS 2017 and dont use VS 2015 to work with ASP.NET Core.
Visual Studio 2015 will only support .NET Core <= 1.1 (ie. project.json). If you wish to use .csproj based .NET Core projects you will need to use Visual Studio 2017. You can read about the .NET Core Roadmap here.
You can stick with project.json and Visual Studio 2015. But if you want to move to .NET Core 2.0 you will need to open your project with Visual Studio 2017 which can migrate it to the new .csproj format. You can read about the migration process in this blog post.
Visual Studio 2017 will also provide stable RTM tooling for .NET Core 1.0 (note that the tooling in Visual Studio 2015 is only in preview). There is another interesting blog post here which discusses the move to the new project format, Joe Morris from Microsoft confirms there are no plans to have VS 2015 support the build/project system.
Update
With the release of Visual Studio 2019, the latest .NET Core SDKs are not supported in Visual Studio 2015 or 2017. Here is the compatibility matrix:
Is it possible now to build asp.net core projects converted in Visual Studio 2017 to .csproj format on Team City?
The plugin that JetBrains recommends her: Build, test and deploy .NET Core projects with TeamCity seems to require project.json which is gone in VS 2017.
I expected to get an VS 2017 option in Visual Studio (sln) step after I installed VS 2017 RC but it's not there.
Dotnet core projects can be build using the pluging ".NET Core Support" from Jetbrains instead of the "Visual studio" build step.
Install pluging ".NET Core Support" from Jetbrains in Team city. (remember to restart team city to load the plugin)
Install .net core sdk on build agent if this not already has been done. An update to v.1.1.1 is required if you use the new .csproj with Visual Studio 2017 Core projects
Setup new .Net core task to build project - set name + relative path to project folder in "Working directory":
....This works for me :-)
EDIT:
Team city 10.0.5 contains a Visual Studio 2017 build step (maybe also in 10.0.4 as mentioned in the comment to the question). I have not tried it, as I had problems building VS2015 .net core projects with the Visual Studio 2015 build step and everything worked perfectly with the .Net core build step.
EDIT 2:
I now use the "publish" command as it collects all dependencies from the build + .net core dependencies into the output folder (and the team city build artifacts), ready for deployment :-)