-
Notifications
You must be signed in to change notification settings - Fork 25
DotNetHost path when compiling with Mono's MSBuild #75
Comments
Hi @mrward . Yes atm i suppose build is with dotnet core sdk run by We can fix it as you said, using Should be safe, because now in rc4 |
@mrward as a related note, i asked msbuild team to provide a property to know who is invoking |
@eerhardt @rainersigwald @jeffkl @nguerrera @dsplaisted @piotrpMSFT any idea if there is a property with path of dotnet host? Or if doing like proposed by @mrward using relative to |
No, no property like that currently. Since you have a Mono I don't like finding (sorry, I typed this up but never hit "comment" . . . hopefully better late than never) |
Also if i can use Well for sdk 1.0 the I'll open an issue in sdk to discuss future for sdk 2.0 Thx a lot @rainersigwald for feedback |
@mrward the FSharp.NET.Sdk v1.0.1 is published on nuget and contains this fix. Please update me if there are other issue with mono/vs on mac, or things work. I'll try to add soon mono CI to this repo with #78 |
Visual Studio for Mac uses MSBuild that ships with Mono 4.8.0 to compile .NET Core projects. With F# projects this currently fails since the FSharp.NET.Core.Sdk.targets assume that the dotnet host executable ships with MSBuild which is not the case for Mono.
Building with Mono:
Building with dotnet:
FSharp.NET.Core.Sdk.targets:
Visual Studio for Mac can compile F# .NET Core projects if the MSBuildExtensionsPath property is set to point to the correct .NET Core Sdk folder. However I am wondering if this the best way to solve this. Would it be possible to configure _DotNetHostExecutableDirectory property through another MSBuild property other than MSBuildExtensionsPath? So the FSharp.NET.Core.Sdk.targets would have something like:
Or perhaps better use the MSBuildSDKsPath property which is used with the Microsoft.NET.Sdk MSBuild targets:
The MSBuildSDKsPath points at the Sdks directory:
/usr/local/share/dotnet/sdk/1.0.0-rc4-004771/Sdks/
The text was updated successfully, but these errors were encountered: