Best strategy to keep a CA solution up to date #1475
-
|
I noticed there has been quite some work done on the CA solution in the past weeks. Given that I started a recent CA project a few weeks ago, what would be the best/most convenient/solid strategy to keep my solution up to date with latest and greatest improvements? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
Hi @mrhighstone, There's no automated upgrade mechanism - that's a limitation of the
Note: I haven't released a new version of the template yet - still working through the dependency upgrades. Once that's done I'll publish a new version to NuGet. Hope this helps! |
Beta Was this translation helpful? Give feedback.
-
|
Ha, that is what I expected, and used so far. Good to have this documented anyway |
Beta Was this translation helpful? Give feedback.
Hi @mrhighstone,
There's no automated upgrade mechanism - that's a limitation of the
dotnet newtemplate system itself. Here's the approach I recommend:dotnet new uninstall Clean.Architecture.Solution.Templatedotnet new install Clean.Architecture.Solution.Template::X.X.Xdotnet new ca-slngit initgit add .git commit -m "Initial Commit"dotnet new install Clean.Architecture.Solution.Templatedotnet new ca-sln --force