- ABP Framework version: v5.2
- UI type: Angular
- DB provider: EF Core
- Tiered (MVC) or Identity Server Separated (Angular): no
• We develop open source software using abp framework. Afterwards, we want to add paid developments in our project, and we will use abp commercial modules in these developments. (ex: two factor authentcation) • What method should we follow to do this with minimal code changes? • Is there a video / example of this?
10 Answer(s)
-
0
Good question. I would also like some feedback in general of how to use ABP Commercial in an open source project, if it is all doable and if so how to do it without breaking any licenses etc. There might already be some article etc on this but haven't seen anything and thought about it from time to time.
-
0
Hi support,
do you have a suggestion?
Thanks.
-
0
hi
You just need to add the
commercialpackages to your project. You can check thecommercialtemplate project. -
0
thanks maliming, we were able to add and use commercial packages.everything is fine.
-
0
: )
-
0
hi
You just need to add the
commercialpackages to your project. You can check thecommercialtemplate project.Does this mean that we can include commercial packages in open source then on GitHub etc without breaking the license? Will it still be something that a non ABP customer could still compile even though they probably could not use it? Mostly interested in the legal aspects here so that we don't break any rules etc. Thanks.
-
0
hi
You can't make public the
commercialsource code or packages.https://commercial.abp.io/faq
-
0
hi
You can't make public the
commercialsource code or packages.https://commercial.abp.io/faq
Hi,
I've read that already but I don't think it really answers the question. I also don't see anything in there about distributing the applications to clients (with or without the source code) like when you build a system for a client. Ie the FAQ seems to be lacking information about runtime vs development time etc. We have just assumed that it is probably working in the same way as other tooling, like development time licenses for DevExpress, Telerik etc.
(We have yet to actually build and distribute a real application with ABP, but we plan to do it in the future).
-
0
This is the only thing I've been able to find about this:
"12.2 ABP Commercial products cannot be publicly shared or cannot be licensed as an open-source product without asking written permission of Volosoft Bilişim Anonim Şirketi. "
-
0
As stated in https://commercial.abp.io/eula, you cannot make the commercial project as open-source. I think it's very understandable. Otherwise, some people can purchase a Business License and share all the source code on the internet.
But the major question here is, using commercial modules with the free project template. In this case, the developer will not share the source code of the commercial packages but will use the binary files. This is technically probable.
On the other hand, you can distribute your commercial project to anyone without the source code, there's no restriction on that. But when you deliver with the source code, then the target customer also needs to purchase a license, otherwise, they will occupy your developer seats which is not a desired result.
