Hello,
We hold an ABP commercial license (organization: Tribulus Development AB) and run a production application on ABP 10.6.1 / .NET 10 with an Angular UI. We are evaluating whether to renew, and we want to understand exactly what we may and may not do after the license period ends, so that we stay within the terms. We would appreciate written answers to the questions below.
Context: we use these pro modules: SaaS, File Management, Payment, Identity Pro, Account Pro, OpenIddict Pro, Language Management, Text Template Management, GDPR, Audit Logging Pro, and the LeptonX theme. While our license is active we have downloaded their source code with "abp get-source" and the Angular package source with "abp add-package <name> --with-source-code", and confirmed the solution builds with the modules referenced as project/source references instead of NuGet/NPM packages.
License code after expiry The FAQ says the license is perpetual and that we can continue developing existing applications after it expires. Does our existing AbpLicenseCode continue to pass the license check indefinitely for version 10.6.1, both for the NuGet packages and for the modules built from downloaded source? Does this hold in development (debug) as well as in production, and on new developer machines and new servers?
Downloaded source after expiry May we keep using, modifying and maintaining the pro module source code we downloaded during the license period, inside our private repository, for this same application, after the license expires?
Upgrading the framework under our own maintained source The downloaded source references the package Volo.Abp.Commercial.Core and calls LicenseChecker.Check<TModule>() in each module class. If, after expiry, we upgrade the open-source ABP framework packages (for example to ABP 11 or a later .NET version) and maintain the pro module source ourselves: a) Is Volo.Abp.Commercial.Core 10.6.1 expected to keep working against newer Volo.Abp.Core versions, and will our license code still validate in that setup? b) If it does not, are we permitted to remove the LicenseChecker calls and the Volo.Abp.Commercial.Core reference from our own copy of the source? If this is not permitted, what is the supported path?
Package feed and registry access after expiry Will our private NuGet feed (nuget.abp.io) and the commercial NPM registry keep serving the versions released during our license period (10.6.x, LeptonX 5.6.x)? Our CI restores packages on every build. Are we allowed to mirror those package versions to an internal, private feed (for example Azure Artifacts) used only by our own team and build servers?
Remaining closed packages Is source code available for Volo.Abp.AspNetCore.Mvc.UI.Theme.Commercial and for Volo.Abp.Commercial.Core? If so, which CLI module or package name should we use?
Developers After expiry, does the developer-seat limit still apply to who may work on the application and on the downloaded source?
Is there anything else that stops working at expiry that is not listed in the FAQ (for example ABP Studio, the CLI login, or "abp update" within 10.6.x)?
We are asking so that we can make the renewal decision with a clear picture and remain compliant either way.
Thank you.
3 Answer(s)
-
0
Please contact us at https://abp.io/contact.
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
Hello again, is it possible to get an answer for the questions?
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
Hi,
- License code after expiry The FAQ says the license is perpetual and that we can continue developing existing applications after it expires. Does our existing AbpLicenseCode continue to pass the license check indefinitely for version 10.6.1, both for the NuGet packages and for the modules built from downloaded source? Does this hold in development (debug) as well as in production, and on new developer machines and new servers?
Yes, it keeps passing after the license period ends, in Debug and in Release, on new machines and on new servers. Keep
AbpLicenseCodein the configuration of every deployed application, otherwise the application stops withABP-LIC-ERROR. A server needs nothing else. A developer machine needsabp loginand access to abp.io, becauseDevelopmentmode and an attached debugger also do an online check, and that one passes after expiry as well.- Downloaded source after expiry May we keep using, modifying and maintaining the pro module source code we downloaded during the license period, inside our private repository, for this same application, after the license expires?
Yes, for this application. After the period ends
abp get-sourcestill works for the versions you have access to, as long as you pass--versionand the commercial NuGet source is in your globalNuGet.Config.- Upgrading the framework under our own maintained source The downloaded source references the package Volo.Abp.Commercial.Core and calls LicenseChecker.Check<TModule>() in each module class. If, after expiry, we upgrade the open-source ABP framework packages (for example to ABP 11 or a later .NET version) and maintain the pro module source ourselves: a) Is Volo.Abp.Commercial.Core 10.6.1 expected to keep working against newer Volo.Abp.Core versions, and will our license code still validate in that setup? b) If it does not, are we permitted to remove the LicenseChecker calls and the Volo.Abp.Commercial.Core reference from our own copy of the source? If this is not permitted, what is the supported path?
a) Yes for newer 10.x versions, and your license code is not affected by the framework version. ABP 11 is not released yet, so I can't answer for that one today.
b) You don't need to. The package you already have keeps working, so staying on it is the supported path.
- Package feed and registry access after expiry Will our private NuGet feed (nuget.abp.io) and the commercial NPM registry keep serving the versions released during our license period (10.6.x, LeptonX 5.6.x)? Our CI restores packages on every build. Are we allowed to mirror those package versions to an internal, private feed (for example Azure Artifacts) used only by our own team and build servers?
Yes, 10.6.x and LeptonX 5.6.x keep being served and your CI keeps restoring. The limit after expiry is the last major.minor released before your license end date, so if 10.7.0 ships before that date you get 10.7.x as well. The Angular packages are on the public npm registry, so nothing changes for
npm install. An internal feed that only your own team and build servers use is fine. Sharing the packages outside your organization or publishing them is not.- Remaining closed packages Is source code available for Volo.Abp.AspNetCore.Mvc.UI.Theme.Commercial and for Volo.Abp.Commercial.Core? If so, which CLI module or package name should we use?
No, there is no source code for those two packages. They stay as NuGet packages.
- Developers After expiry, does the developer-seat limit still apply to who may work on the application and on the downloaded source?
Yes, the seat limit still applies, and it is the count that matters, not the specific people. You can move a seat to another person after expiry without any additional cost, and it stays 2 machines per developer.
- Is there anything else that stops working at expiry that is not listed in the FAQ (for example ABP Studio, the CLI login, or "abp update" within 10.6.x)?
One thing the FAQ doesn't mention: after the period ends the CLI no longer gets your organization's NuGet API key and license code from abp.io. Both are already in your solution, the key in
NuGet.Configand the code in your application configuration, so keep them safe.abp loginkeeps working. For a patch inside 10.6.x, set the versions in your csproj files instead of runningabp update.Thanks
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
