Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Forge 3.0 #115
World has changed. We know live in era of .Net Core and what’s even more important in the era of .Net SDK and
Moving Forge to .Net Core seems a good move as we are trying to move all the F# project there I think :).
Can a CLI global tool be used locally ?
Like we did in the past using
I am asking this because I am still wondering if global tool are something nice... I mean, you don't always want the same version for all your projects etc. So if user can decide, it ok :)
I am not sure to understand the point n°3. The idea is to provide an easy plug-in to FAKE/Paket for template that don't use one of them ? Should't we try to add the support to the template instead ? We could use conditional choice for that.
Last point seems like a good idea, only if Forge do not modify what it don't understand. For example, on a Fable library forge always remove this lines:
<!-- Add source files to "fable" folder in Nuget package --> <ItemGroup> <Content Include="*.fsproj; **\*.fs" PackagePath="fable\" /> </ItemGroup>