ASP.NET Zero is built by team behind ASP.NET Boilerplate. So, it's the best UI and application implementation of the framework. Everything in ABP can be directly used ASP.NET Zero. All documentation is valid for ASP.NET Zero too. Since ABP has a comprehensive documentation, it will help a lot while developing your application.
ASP.NET Boilerplate web site provides a free startup template to simply start with the framework. ASP.NET Zero is a production ready enterprise level application base. See comparison table for differences between free startup templates and ASP.NET Zero.
Our licenses have product count restrictions. For example, if you buy a Regular license, you can use it to develop one real product/solution. You can create test/demo projects without any restriction. You can also re-create (re-download) the same project whenever you need. However, you should buy higher licenses if you want to develop more than one product/solution using ASP.NET Zero. You can sell your product to any number of customers or deploy to more than one environment. No restriction here.
ASP.NET Zero license has also developer count restriction. Regular license allows up to 3 developers actively working on your ASP.NET Zero based solution. If you have a larger team, you should consider to buy higher licenses.
ASP.NET Zero licenses include 1-year upgrade and premium forum support. You will also have access to Github repository and watch all changes on ASP.NET Zero.
After your license perid ends, you can continue developing your application and use ASP.NET Zero forever. Also, you can always update ASP.NET Boilerplate and module-zero nuget packages, since they are open source projects and will always be open source. You can continue to access all documentation since it's public. But you will not get ASP.NET Zero upgrades anymore, can not access to Github repository. Also, your premium forum membership ends. You can surely use community section of the forum as always.
If you want, you can extend your license 1-year more by 50% of your purchased license's current price. If you want to extend your license, you should do it until 1-month later of your license expire date.
Yes, you can upgrade to a higher license by just paying the price difference. Upgrades should be requested in first 3 months of your license period. Your license period is automatically extends when you upgrade. You can use license management page to extend your license. Mail to email@example.com if you need to help.
We can split updating to 2 parts:
1 - ASP.NET Boilerplate (the framework) and module-zero (base domain logic for user, role, tenant... management).
They can be easily updated since they are distributed on nuget. Here, a list of all nuget packages:
New releases generally are backward-compatible. If there is a breaking change, we add it to relase notes and document how to migrate. You can upgrade these nuget packages even after your license period ends, since they are open source. So, upgrading this part is easy. Just update nuget packages.
2 - AspNet Zero - the startup template: UI views and application services
This part is not developed as a 'closed' framework/library. Because different companies have very different needs and you will want to extend/change UI upon your needs. That's why we call AspNet Zero as a starter kit/template: All source codes of ASP.NET Zero is on your hands, you can freely modify it upon your needs.
In most cases you don't have to upgrade if you are happy with your solution. Even you might built the same feature yourself before us. If you like new features, you should adapt changes to your existing solution. In this case, Github repository will help you much (github.com/aspnetzero/aspnet-zero, requires purchasing ASP.NET Zero to access). You can compare releases and copy changed parts to your solution. For example, assume that we enhanced Audit Logs page with new features and you want to get these new awesome features. If you did not change this page, you can directly override your page and related classes. If you did change it, then you can see changes on Github and you can merge changes to your code. We also advice you to review each commit to check if it's also needed for you. Because some of they can be bugfixes.