Conversation
…eNoUnusedFsSrGenResources msbuild prop)
|
@dotnet-bot test this please |
|
ok, ready to review/merge. the |
src/FSharpSource.targets
Outdated
| </Target> | ||
|
|
||
| <Import Project="..\lkg\FSharp-$(LkgVersion)\bin\FSharp.SRGen.targets" /> | ||
| <Import Project="..\packages\FSharp.SRGen.Build.Tasks.2.0.0\content\FSharp.SRGen.targets" /> |
There was a problem hiding this comment.
nit: Can you add this path as well to the above properties? since we are using that group to keep track of all nuget versions.
0152d76 to
ca9d289
Compare
|
ok parametrized FsSrGen packages versions, thx @otawfik-ms |
|
Thanks @enricosada |
|
@enricosada I notice from GitHub that you have a dotnetcli built version of fsSrgen is there a nugget package containing that ? |
|
@KevinRansom yes. I'll post tomorrow a coreclr branch with my wip dotnet cli build of fsharp.compiler. |
|
Btw these packages are .net 4.6 but are built with dotnet cli and the coreclr fsc, no fsproj |
…rgen_package"" This reverts commit b297b1a.
ref #962
the FsSrGen use .NET 4.6 instead of .NET 3.5