3 Answer(s)
-
0
There are no guided steps. See this reply:
Unfortunately not. We are working on migrating to metronic for two months and it is not a straight forward migration to do.
Best way you can try is, download the new version with your existing project name and merge it into your existing solution. But, there are also some changes [made] on the solution structure for new Xamarin application which will make merging a bit harder.
How to migrate existing solution: https://github.com/aspnetzero/aspnet-zero/issues/96#issuecomment-268093697
-
0
There aren't any posted that I'm aware of, its no different than going from v 4.5 to v4.6 except v5 changed out metronic 4 for 5 so all the styles and classes changed... But the process of conversion is your own.
My process was push v5 to our aspnetzero base branch (This is just stock package download from site). I then made a new feature branch based of this base branch (Normally you would feature off of your primary dev branch). Then I started moving files individually over to this new branch feature by feature. All the c# code moves fine, you might need to put some of the files in to the "shared" projects if youre following their structure and want to do the mobile app. Then I update my "views" with the new bootstrap4/metronic5 styles (Luckly for us we use devextreme for most of our stuff so it was just changing out some wrapper portlets and boom, done). I spent most of my time fixing/tweaking/learning the gulp process, tweaking our VSTS build sever process. But since we didn't have a lot of custom html and mainly just devextreme controls it made the conversion super easy since the controls generate the output of the code. In all it probably took about 20hrs to do the upgrade and 10 of that was messing with flexbox to make the devextreme grid resize properly when the browser resizes and constraining it to the flexbox area. Now that I have our new branch done, I think I'm going to rename our old dev to v4 dev and make a new one with based of the final status of this v5 conversion feature branch. And since I went thru the conversion all our "InDev" work can be easily converted over once they get finalized into the old 4.6 dev branch.
If you have lots of views time will vary to convert to the new metronic5 styles. Since there was so many structure changes not sure if you could easily pull the changes in. For us it was faster to do the above approach, I also got to refactor some code from when we first started with aspnetzero and did some things a little different early on ;)
-
0
@BBakerMMC Thanks for sharing your experience :)
