Request to simultaneously support both Paket dependency management and CPM options

[0xLiao]

As a fan of MiniScaffold, I've long used it to build my projects and update older ones according to template changes. However, in the most recent template update, I found that Paket has been completely removed, which is confusing. I don't understand the advantages of CPM that would lead to Paket being entirely abandoned.

Can you tell me why Paket was completely deprecated in favor of fully embracing CPM? I want to see if I can convince myself to switch to CPM.

Or could the next version provide an option to support both dependency managers?

Thank you very much for developing such a high-value template.

[TheAngryByrd]

Thanks for the questions!

Can you tell me why Paket was completely deprecated in favor of fully embracing CPM? I want to see if I can convince myself to switch to CPM.

The maintenance for paket has stalled, and there isn't much movement on getting new maintainers. Additionally, every version of .NET coming out needs a PR for paket to understand new TFMs and 10 hasn't been merged yet, preventing being able to upgrade projects to test against net10. Also, Paket is frustrating to use in complex MSBuild scenarios. And unfortunately, having to translate nuget -> paket is frustrating for newcomers.

Nuget is definitely still missing some features (notably Centralized lock files) or other kinds of dependencies. Which sucks to lose unfortunately, unless the maintenance situation changes, I can't promote it anymore. As much as I wish otherwise.

Or could the next version provide an option to support both dependency managers?

I don't really see a way with the current dotnet templating system that doesn't involve lots of duplication. It's the same reason I don't have other unit testing frameworks.

Thank you very much for developing such a high-value template.

Thanks for the kind words!

[0xLiao]

Thank you very much. I understand now.