-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
cannot build latest master #36840
Comments
Tagging @dotnet/roslyn-infrastructure @jasonmalinowski |
@CyrusNajmabadi I just pulled, cleaned, restored and built master OK. However the latest .NET Core SDK I have is 3.0.100-preview6-012105 which matches what is specified in the global.json. I am going to download the -012264 build of the SDK and give it a try to see if I can reproduce what you are seeing. |
I've hit this before as well |
@dibarbet Thanks, unfortunately that didn't help. I have no msbuild instances running. @JoeRobich Where can i find that version of the .net sdk? |
@CyrusNajmabadi I was able to build with the same version of the SDK that you have installed, using the same version of VS. Did you have other versions of VS open? If so were they preview or RTM versions? |
@CyrusNajmabadi We link to it in the Building, Debugging, and Testing on Windows, but you can download it here - Windows x64 installer. Not sure if your issue is SDK related anymore. |
I have no other versions of VS open. I even rebooted to try to get things into a good state. |
|
the former. Thanks! |
I am now also running into the issue again, and my former fix is no longer working. |
@CyrusNajmabadi All it took was leaving VS up overnight I suppose. |
Any ideas on how to fix this. @jasonmalinowski @dotnet/roslyn-infrastructure ? |
Note: i'm also still getting this:
|
Something strange seems to be happening on build too. It seems to be trying to restore all packages every time i try to build. This takes a looong time. like 20s just to do that step. |
I get this error:
I have cleaned and restored. I am on:
The text was updated successfully, but these errors were encountered: