Upgrade to Pro possible?

#1 · February 16, 2018, 6:46 am

Hi Eben, first of all, thanks for this template, it has the level of complexity and engineering I was looking for my current project.
I've already setup the free version and:
-Have no issues setting up with VS 2017 CE 15.6
-Branded the app
-Stripped out unnecessary code
-Implemented a couple of pages
-Touch the demo data so I can show the skeleton and get approval.

My question is: I'm thinking to move to Pro ( because of Material design & appreciation), is there a clean upgrade path?

#2 · February 24, 2018, 3:46 pm

Quote from Eben Monney on February 24, 2018, 3:46 pm
Migrating the Backend (ASP.NET Core)

The backend is very compatible with the opensource version and merging your changes into PRO should be straight forward.
The significant changes are described below:

DAL Project: The API surface of DAL remains unchanged except with some code enhancements. This is a drop-in-place update if the files remain unchanged in your project

QuickApp.Pro: Project follows the same architecture as the free version with some technology replacements such as IdentityServer4 for OpenIdDict and some code optimizations. The changes are mostly backward compatible with the opensource version. The incompatible changes are focused in these files:

AuthorizeCheckOperationFilter.cs - Added

IdentityServerConfig.cs - Added

ProfileService.cs - Added

Startup.cs - Modified

AuthorizationController.cs - Removed

Migrating the Frontend (Angular5)

Migrating the frontend is not linear because of the move from Bootstrap to Angular Material (Migrating from QuickApp to QuickApp standard is a more straight forward approach as the same client technologies are used. i.e. Bootstrap).
Whereas the features are preserved between the two versions of the template the implementation details are different.

For a complete migration your UI Components will need to be rewritten with Angular Material.
It is also possible to keep your existing custom bootstrap components and cherry-pick the components you'll want to migrate to Angular material. It is possible to have the 2 libraries (Bootstrap and Angular Material) in the same project.
This gives you the flexibility to quickly move to Angular Material and gradually migrate your existing components as you see fit.

Do note that the API surface of the models and services do not change and are a drop-in-place upgrade.

Please do a DIFF between different versions of QuickApp for a view of all the changes at the file level. Its advisable to have the same base namespace in the comparing projects to avoid all files reporting as different.

Beyond Compare is a good diff/merge tool I'll recommend for this kind of task.

Migrating the Backend (ASP.NET Core)

The backend is very compatible with the opensource version and merging your changes into PRO should be straight forward.
The significant changes are described below:

DAL Project: The API surface of DAL remains unchanged except with some code enhancements. This is a drop-in-place update if the files remain unchanged in your project
QuickApp.Pro: Project follows the same architecture as the free version with some technology replacements such as IdentityServer4 for OpenIdDict and some code optimizations. The changes are mostly backward compatible with the opensource version. The incompatible changes are focused in these files:
- AuthorizeCheckOperationFilter.cs - Added
- IdentityServerConfig.cs - Added
- ProfileService.cs - Added
- Startup.cs - Modified
- AuthorizationController.cs - Removed

Migrating the Frontend (Angular5)

Migrating the frontend is not linear because of the move from Bootstrap to Angular Material (Migrating from QuickApp to QuickApp standard is a more straight forward approach as the same client technologies are used. i.e. Bootstrap).
Whereas the features are preserved between the two versions of the template the implementation details are different.

For a complete migration your UI Components will need to be rewritten with Angular Material.
It is also possible to keep your existing custom bootstrap components and cherry-pick the components you'll want to migrate to Angular material. It is possible to have the 2 libraries (Bootstrap and Angular Material) in the same project.
This gives you the flexibility to quickly move to Angular Material and gradually migrate your existing components as you see fit.

Do note that the API surface of the models and services do not change and are a drop-in-place upgrade.

Please do a DIFF between different versions of QuickApp for a view of all the changes at the file level. Its advisable to have the same base namespace in the comparing projects to avoid all files reporting as different.

Beyond Compare is a good diff/merge tool I'll recommend for this kind of task.

Ingo and romeo.adjam have reacted to this post.

#3 · March 26, 2018, 2:51 pm

I would like to brand the app as well. What is the best practice to do so?

IMPORTANT!

This forum is now archived. Click here for the New Support Forum