Closed tpetricek closed 9 years ago
@Krzysztof-Cieslak can give you a better answer, but I'll try it anyway.
Most of templates are still work-in-progress and feedback is very welcome.
Today you can decide before template installation if you want to use nuget or paket. If you choose Nuget you'll have to add the version to the #load directive as you noticed, otherwise the template is converted to use paket and the version is not needed anymore.
Yeah, that makes sense.
For FsLab, I would probably prefer just using Paket no matter what, but I can see that having a choice is nice. The version numbers in NuGet are causing all sorts of troubles and all samples on fslab.org are written assuming that you are using Paket - so if someone decides to use NuGet, they'll probably have harder time... (And I assume people might pick NuGet, just because they know what it is).
As for now, I've assumed that templates are uploaded with packages.config
files. During installation we ask user If he wants to use Paket (and yes
is default answer ;) ) and if so Paket's convert-from-nuget
is used to convert it from packages.config
to paket.references
and paket.dependencies
(Right now I assume "solution" like setup, and create .paket
folder and .paket.dependencies
in folder I run generator from and put template in subfolder). I've tested both FsLab templates with Paket and it's working.
Personally I would love to use only Paket for all templates, I'm not sure if it would not be problem for users.
This looks very cool - I don't have everything setup to check this out (sadly!) but I was looking at the FsLab templates and I was a bit surprised to see
packages.config
there. Does that mean that the project will use NuGet?The FsLab templates require Paket - that is, they do not work if you have version number in the folder name, because they always reference FsLab etc. through something like:
Am I missing something, or are some of the templates still work-in-progress?