Hello,

We develop large system based on metadata-driven architecture and we consider using ORM LLBLGen. The idea that a user (not a developer) will create entities and relations between them in our designer (web application).

Thus, we will generate code ourselves and does not need LLBLGen designer itself while we consider ORM.

It would be great if you could answer the following questions: 1. Do you foresee any problems if we use LLBLGen as I described above? 2. Is there console (command line) version of LLBLGen designer or any other way to simplify generating of our code? 3. How we license it? (I mean using LLBLGen ORM without UI designer)

Thanks, Andrey

Every user operating licensed parts of the designer (model engine + code generator falls under that) needs to have a license. So for every user of your app you have to purchase a license, you can't purchase 1 license and then let the world use it.

You effectively have to embed the designer core in your webapplication, which runs into problems as well. It's designed to be usable without the GUI layer, but that doesn't mean it's a dll you can simply include and run.

There are 2 types of users in our system - regular users and administrators. Only administrators can create new entities and forms and we could buy licenses for them.

Are there examples and documentation how could the designer be used without GUI?

andrey wrote:

There are 2 types of users in our system - regular users and administrators. Only administrators can create new entities and forms and we could buy licenses for them.

Are there examples and documentation how could the designer be used without GUI?

No, as we don't want others to use the designer core without us knowing it. We have to trust you you won't create a designer from our code and that only administrators will use it, and you'll buy a license for every user using the designer core.

I'm sorry, but without a tight contract that's not going to work. As you're in Russia, we won't do that as we don't have the proper systems in place to protect our work: we don't relicense our designer core to 3rd parties at this time.