Personally I feel that we should provide in templates paket.references files instead of packages.config. However it can limit usage for people who are not using Paket. Another problem is how to add packages to "solution" level paket.dependencies file having only paket.references files from templates. /cc: @forki
Maybe we should make users able to choose between Nuget and Paket? We could provide 2 types of templates - Nuget and Paket - and allow user to choose which one to choose. Or provide only Nuget type of template and run paket conert-from-nuget when user choose Paket version?
Some templates also requires Nuget packages to be used. Example of it is WebAPI template provided by @rodrigovidal (https://github.com/fsprojects/generator-fsharp/pull/4/files).
Personally I feel that we should provide in templates
paket.referencesfiles instead ofpackages.config. However it can limit usage for people who are not using Paket. Another problem is how to add packages to "solution" levelpaket.dependenciesfile having onlypaket.referencesfiles from templates. /cc: @forkiMaybe we should make users able to choose between Nuget and Paket? We could provide 2 types of templates - Nuget and Paket - and allow user to choose which one to choose. Or provide only Nuget type of template and run
paket conert-from-nugetwhen user choose Paket version?