Frequently Asked Questions

ASP.NET Zero is a Visual Studio solution. It's built based on layered architecture and other software best practices. It provides a SOLID, strong and scalable solution architecture, pre-built pages and much more.

If you have a business idea and want to build a web application, then you can take ASP.NET Zero as your base solution to not waste your time on building common requirements like user, role and permission management, audit logging, setting management, user profile management, localization and so on (see the feature list).

It not only provides many pre-built functionalities, but also makes your daily development work easier by using a complete web application framework: ASP.NET Boilerplate

It also supports multi-tenancy, subscription and payment systems if you want to create a SaaS application.

It's built on already-known tools like ASP.NET Core, Entity Framework, Angular and so on...

It uses the Metronic theme for the user interface.

You get the full source code and can change it freely based on your business requirements!

  • It provides a layered, well-defined and documented architectural model. So, your developers will know how to write code that follow best practices.
  • The solution is mature and has solved most of the issues faced when creating an application from scratch.
  • It provides many pre-built functionalities that are common to almost every application: login, user, role and permission management, audit logs, settings, user profile, multi-language, multi-tenancy and so on. Create a demo to see most of the UI.
  • It's based on the open-source and community-driven ABP framework. It is actively used by thousands of developers and is continuously developed. It makes your daily development easier by providing base classes and infrastructure, and automates your repeated tasks.

So, don't waste your time on common requirements, begin to develop your business idea from the first day.

ASP.NET Zero is built by the team behind ASP.NET Boilerplate. So, it's the best UI and application implementation of the framework. Everything in ABP can be directly used in ASP.NET Zero. All the 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 website provides a free startup template to simply start with the framework. ASP.NET Zero is a production-ready enterprise-level application base. See the comparison table for differences between the 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 also has a developer count restriction. Regular license allows up to 3 developers who are actively working on your ASP.NET Zero–based solution. If you have a larger team, you should buy higher licenses.

Notice that the license system checks only during development. It does not check on the production instance, because the license does not have a limit on deployment count. It also does not force you to be connected to the internet both during development and in production.

ASP.NET Zero includes the full Metronic license. You can use Metronic with ASP.NET Zero under our terms and restrictions. For example, Metronic normally requires an Extended license for SaaS projects, but you can use it with ASP.NET Zero in your SaaS application without any additional cost. One restriction here: You cannot buy ASP.NET Zero and just use Metronic independently in your non-ASP.NET Zero–based projects. You can only use Metronic in ASP.NET Zero.
Yes, we sell the source code. So, you can completely change it based on your requirements. There are two exceptions of that:

1. The solution uses many libraries as nuget packages. But they are all free and open source. Including all of their source code into the solution is not a good idea. Because then your solution grows too much and you can not update the libraries easily. However, if you need the source code of any library, you can just get it from it's repository. ABP framework is also like that and it's available on the Github repository. So, there is no hidden code in that manner.

2. The solution also has a closed-source nuget package that is used to protect AspNet Zero's license rules. This closed source library has also a few application-independent utility classes those are not subject to change for your application, but to make the application depending on the licensing library. Notice that AspNet Zero's license control is done only in the development time and only in your license period. You can continue to develop and use the source code (even without the developer count restriction) after your license period ends.
ASP.NET Zero uses Metronic as the UI theme. Metronic is one of the world's most popular, strongest and richest UI themes, probably even the first. That's why we have chosen it. When you buy ASP.NET Zero, you will have access to all Metronic theme layouts and components. You can use all of them in your applications.

ASP.NET Zero license includes 1-year upgrade and premium forum support. You will also have access to the GitHub repository and track the changes on ASP.NET Zero.

After your license period ends, you can continue developing your application and using ASP.NET Zero for a lifetime. Beside, you can always update ASP.NET Boilerplate and module-zero NuGet packages, since they are open-source projects (and will always remain as open-source). Since you it's public, you can continue to access all the documentation. But you will not get ASP.NET Zero upgrades anymore and you will not have access to the GitHub repository. Also, your premium forum membership will be ended. You can get support from the community as always.

You can extend your license by 1-year more for 50% of your purchased license's current price. If you want to extend your license, you should do it within 1-month after your license expires.

Yes, you can upgrade to a higher license by just paying the price difference. Upgrades should be requested within the first 3 months of your license period. Your license period is automatically extended when you upgrade. You can use the license management page to extend your license. Mail to info@aspnetzero.com if you need help.

We can split updating into 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's a list of all the NuGet packages:

http://www.aspnetboilerplate.com/Pages/Documents/Nuget-Packages
http://www.aspnetboilerplate.com/Pages/Documents/Zero/Nuget-Packages

New releases are generally backward-compatible. If there is a breaking change, we will add it to the release 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 the NuGet packages.

2 - ASP.NET Zero - the startup template: UI views and application services

This part is not developed as a 'closed' framework/library. Since different companies have very different needs, you will want to extend/change the UI for your needs. That's why we call ASP.NET Zero a starter kit/template: All the source code of ASP.NET Zero is in your hands, so you can freely modify it for your needs.

In most cases, you don't have to upgrade if you are happy with your solution. You might even build the same feature yourself before us. If you like the new features, you should adapt the changes to your existing solution. In this case, the GitHub repository will help you much (github.com/aspnetzero/aspnet-zero, requires purchasing ASP.NET Zero to access). You can compare releases and copy the changed parts to your solution. For example, assume that we enhanced the 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 replace your page and related classes. If you did change it, then you can see the changes on GitHub and merge the changes into your code. We also advise you to review each commit to check if it's needed for you, because some of them can be bug-fixes.