-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nullability annotation for scaffolding #19401
Conversation
Resubmitting after reverted by cb686e849b448ebbafe9dfee5288d4610bc9823c (cherry picked from commit eab93af)
@roji Still failing for me; IDE details below. Assume this is working on Linux with the same IDE? (By working I mean that you can open JetBrains Rider 2019.3.1 |
Yeah, a full rebuild of All.sln works for me, both within Rider and on the command-line with
|
|
@ajcvickers so I understand correctly, you can build this branch from the cmdline, but when you build it from Rider you get compilation errors? That could indicate that maybe you're using some special dotnet CLI or something, can you please check out File->Settings->Build, Execution, Deployment->Toolset and Build? The important bit is probably the .NET Core CLI executable path, which in my case is /usr/share/dotnet/dotnet (the global/system-wide place for .NET SDK installations, should be the analogous path in Windows...). |
@aspnet/efteam can someone else confirm that they can properly build this branch from an up-to-date VS? |
@roji But when using our build system we install and use a local SDK. Hence:
We shouldn't be using whatever is installed on the machine. |
@roji I think I figured it out somewhat. The clue was in that settings page. Instead of using the auto-detected MSBuild (which came from VS) I changed it to use the local MSBuild: |
Oh weird... So the VS-provided MSBuild is too old or something? 🤷♂
You're right - up until 3.1 I my EF's Rider settings were pointing to the EF-provided dotnet SDK, but since for now we're at vanilla 3.1 it seems a bit easier to just hack on EF as if it were just any normal open source project out there :) Until we pin to some other SDK that is. Anyway thanks for looking into it, will merge now. |
Resubmission of #19321, reverted by cb686e849b448ebbafe9dfee5288d4610bc9823c.
Already reviewed and approved, @ajcvickers needs to confirm that it's working on his environment.