You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Any project that is build in F# will as a general rule depend on FSharp.Core. YoloDev.Dnx.FSharp itself also depends on FSharp.Core, but since it's normally added as a build time only dependency, it's dependency on FSharp.Core doesn't get transferred to the project produced by it. I think there should either be an API that allows me to inject dependencies into the project being built by the custom compiler, or at least some way to note that FSharp.Core should be transfered as a dependency to peer projects even if YoloDev.Dnx.FSharp is listed as built-time only.
The problem is that as it stands now, if people forget to add the dependency on FSharp.Core, everything will build just fine, but will break at runtime, which is a really bad situation.
…0200624.3 (#4640)
Microsoft.Build.Localization , Microsoft.Build
From Version 16.7.0-preview-20324-02 -> To Version 16.7.0-preview-20324-03
Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
From @Alxandr on May 30, 2015 17:56
Any project that is build in F# will as a general rule depend on
FSharp.Core
.YoloDev.Dnx.FSharp
itself also depends onFSharp.Core
, but since it's normally added as a build time only dependency, it's dependency onFSharp.Core
doesn't get transferred to the project produced by it. I think there should either be an API that allows me to inject dependencies into the project being built by the custom compiler, or at least some way to note thatFSharp.Core
should be transfered as a dependency to peer projects even ifYoloDev.Dnx.FSharp
is listed as built-time only.The problem is that as it stands now, if people forget to add the dependency on
FSharp.Core
, everything will build just fine, but will break at runtime, which is a really bad situation.Copied from original issue: aspnet/dnx#1994
The text was updated successfully, but these errors were encountered: