-
Notifications
You must be signed in to change notification settings - Fork 783
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
Compiling a F# class library fails when using Visual Studio 16.8 #10447
Comments
Based on the error:
It looks like it was trying to run |
@TIHan is correct, the build is invoking Is there a Otherwise I'm also going to yield to @KevinRansom to answer the question of why we're trying to build through dotnet from within VS. |
I will look at this in a little bit, I just need to finish off a merge. But it looks like something unusual is happening. |
I believe I found the problem. I was getting an error earlier on a different project (also after updating VS to 16.8) that the DOTNET_HOST_PATH was not set. I solved that by setting this env variable to %ProgramFiles%\dotnet\dotnet.exe as mentioned as workaround in this post https://github.com/dotnet/sdk/issues/14497. Probably that was interfering with the fsc build. Removing this ENV variable solves the problem indeed. |
Thats funny I was just typing this: If so you fall into this:
DOTNET_HOST_PATH is normally set by dotnet.sdk when it runs msbuild. It is our understanding that Kevin |
@jcdekoning . Given that the bloody variable is becoming quite famous. I think we may need to reconsider it's use at all. My advice is that it is never the solution to an end user issue. |
@jcdekoning What was the issue that needed to be fixed by setting: DOTNET_HOST_PATH ? |
Oh an asp.net thingy ... I wonder if that is really the correct solution. |
Oh bugger it looks like we can expect asp.net developers to be setting DOTNET_HOST_PATH which eliminates it's usefulness almost completely. Sigh!!!!! |
I will close this, since removing the environment variable DOTNET_HOST_PATH fixed it. |
I updated Visual Studio to version 16.8, which comes with .Net 5, and now a F# class library fails to compile. This also seems to be the case when I create a new solution with a new F# class library.
Repro steps
Expected behavior
A successful build
Actual behavior
The build fails. The complete build log can be found here https://gist.github.com/jcdekoning/0789f4968f72b1a41a890819f05075e0
A snippet which shows the error
Known workarounds
None
Related information
The text was updated successfully, but these errors were encountered: