Closed arphox closed 4 years ago
It seems that I have problems building other solutions as well, e.g. Newtonsoft.Json, currently investigating my installation.
I reinstalled windows 10 on my PC (not just because of this) and installed VS 19 community with a lot of workloads. I can create a lot of types of projects and open my previous ones, but not the solution in this repository, neither the Newtonsoft.Json one.
You need the dotnet SDK listed from global.json:
Thank you, x64 and/or x86 version?
I'm not sure it matters, but I've used the x64 version.
@jnm2 how do I make it more flexible in the selection?
After I installed the .NET Core 2.1.504 x64
package, I could build the solution.
Thank you so much for your help!
@sharwell There's finally documentation: https://docs.microsoft.com/en-us/dotnet/core/tools/global-json?tabs=netcore3x#rollforward
I've been seeing "rollForward": "feature"
the most.
I cannot build the
StyleCopAnalyzers
solution using my installation of Visual Studio 2019 Community.I downloaded the (now) latest commit (b15704e), opened
StyleCopAnalyzers.sln
, and all projects failed to load.When I try to manually reload the
StyleCop.Analyzers
project, an error messagebox appears with the message "The operation could not be completed" and meanwhile I see the following errors in Solution tab of Output window:I have tried to fix the problem by looking at the targeted frameworks for projects, e.g.
netstandard1.1;net452
in case ofStyleCop.Analyzers
, but I did not find any .NET Core references that would be missing.I have most components installed in VS19 installer, click for images
![installimg1](https://user-images.githubusercontent.com/17320094/72869078-571dc400-3ce4-11ea-9326-194d820f399d.png) ![installimg2](https://user-images.githubusercontent.com/17320094/72869094-656be000-3ce4-11ea-8e01-08d37fb5f4c3.png)So I don't understand what could be missing that is related to .NET Core. I did not want to blindly install all legacy .NET Core versions so I am writing this issue.
Also, a "Building" part for the README would be really useful to avoid problems like this.
dotnet --list-sdks
: