Reputation: 1982
Multiple errors converting .net core to csproj
After installing VS2017 RC I realized I needed to upgrade my asp.net core project to work with csproj instead of xproj and project.json.
The upgrade went well, but now I am getting a lot of warnings, and an error.
first, there are warnings regarding the .csproj file. I am getting the following warning - even in a new core class library.
The element 'PropertyGroup' in namespace 'http://schemas.microsoft.com/developer/msbuild/2003' has invalid child element 'TargetFramework' in namespace 'http://schemas.microsoft.com/developer/msbuild/2003'.
I am also getting
The OutputPath is not set for project
Adding an OutputPath in the .csproj file fixes that error, but the OutputPath property is not set in the new class library project I created and it still compiles.
Even after setting the OutputPath, I am getting other errors and warnings, but they don't affect the build (however - and I can't seem to reproduce them in a new project) and even though intellisense is going crazy.
other than that - I am getting over a thousand errors in VS2015 (it can't really load the nuget packages for some reason).
It might be worth mentioning that I am trying to target both .net core and .net461
Upvotes: 0
Views: 162
Answers (1)
Related Questions
- .NET Core solution build gives a GenerateDepsFile error
- .NET Core error on build: error MSB4062 Microsoft.Build.Tasks.ResolveComReference
- .NET Core project reference issues - "Cannot find project info for 'XXX.csproj'"
- Constant errors in asp.net core project
- Strange Build Error .Net Core Project
- .NET 4.7.2 Class Library with simplified csproj format can't be referenced by ASP.NET Core project
- ASP.NET Core error on Build - One or more compilation references are missing
- getting weird compilation errors - .Net Core
- Error after migrating net core preview xproj to csproj
- ASP.Net core RC2 migration csproj reference errors