Hello,
We are putting a lot of weight behind your solution to run much of our technology applications and we have question about managing updates.
I see that we can choose the version of asp.net zero when we purchase a new license.
My question is, if we have a portal in production that is a few years old, and a new version of asp.net zero becomes available. Is there a way to include the new versions of the packages/bundles, metronic theme, or even .NET core version into existing applications that we have in production?
Or, to ask it another way: Is there a way to roll in ALL the new features of a new version into an existing OLDER version of the solution so that we can build and deploy that out so as to stay as up-to-date as possible with the latest version of the asp.net zero solution and supporting technologies?
3 Answer(s)
-
0
I keep a branch called Framework-Master with unmodified asp.net Zero in my repository and merge the updates to my master branch. I think that's the best way to handle updates right now.
-
0
Hi @URITECHNOLOGY,
Basically you have to do it like @rpollak explained. Currently we don't have an officaly way of upgrading to a new version but we will prepare a document for it in the next few days.
-
0
This issue is closed because it has not had recent activity for a long time.
