Skip to content
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

Some users report the csproj files are not getting loaded #36

Closed
carlossanlop opened this issue Mar 3, 2021 · 3 comments · Fixed by #40 or #42
Closed

Some users report the csproj files are not getting loaded #36

carlossanlop opened this issue Mar 3, 2021 · 3 comments · Fixed by #40 or #42

Comments

@carlossanlop
Copy link
Member

Some people are reporting that the tool is not working for them because they are seeing this error when the tool attempts to load the Project instance:

Diagnostic messages found in workspace.OpenProjectAsync - 
D:\runtime\src\libraries\System.Runtime.Intrinsics\src\System.Runtime.Intrinsics.csproj: 
Failure - Msbuild failed when processing the file 'D:\runtime\src\libraries\System.Runtime.Intrinsics\src\System.Runtime.Intrinsics.csproj'
with message: The SDK resolver type "WorkloadSdkResolver" failed to load.
Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.
The system cannot find the file specified. 

Santi and I are investigating it.

@carlossanlop
Copy link
Member Author

carlossanlop commented Mar 4, 2021

We have narrowed down this issue to machines where 6.0 Prev1 is the latest SDK installed. In machines where 5.0 is the latest SDK, it does not repro.

I know this is the case for @tannergooding . @eiriktsarpalis is this your case too?

We are asking the team that owns the problematic APIs to help us with this issue.

@ericstj
Copy link
Member

ericstj commented Mar 4, 2021

Could be caused by the recent changes to pre-req 6.0 preview 1 for dotnet/runtime. If I had to guess it looks like you're loading the latest (6.0) MSBuild in a 5.0 process. Do you need to run in proc? If you need to run in proc then the tool will likely need to run on the same framework version as is pre-req'ed by the repo's global.json.

@ericstj
Copy link
Member

ericstj commented Mar 4, 2021

I hit this and was able to workaround it by making the app target net6.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants