Generate code disable Entity model or derived models generation

Posts   
 
    
Puser
User
Posts: 228
Joined: 20-Sep-2012
# Posted on: 24-Feb-2021 11:28:30   

Hi,

Is it possible to persist the choice I make in the column 'Is enabled' in the 'Generate Code' window? I have some really large projects and need to save time when I only update a single small thing in either a derived model or an entity which is not in a derived model.

daelmo avatar
daelmo
Support Team
Posts: 8245
Joined: 28-Nov-2005
# Posted on: 25-Feb-2021 07:27:55   

Hi Puser,

AFAIK there is not a setting or pereference to remember that selection. You only have to check/uncheck the Generation Task that you need to generate in that moment. Is that an inconvinient for you? What would you like that windows to behave in that matter? Maybe it could be considered as a new feature in future versions.

David Elizondo | LLBLGen Support Team
Puser
User
Posts: 228
Joined: 20-Sep-2012
# Posted on: 25-Feb-2021 09:07:27   

Hi Dealmo,

What would you like that windows to behave in that matter?

To also persist this setting just like the underlying settings.

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39760
Joined: 17-Aug-2003
# Posted on: 25-Feb-2021 09:24:25   

You have to be more clear what it is that you have problems with because if I open a project with an entity model and derived models and generate code, all tasks are enabled. You want to disable some of them and others are enabled and that setup has to be persisted?

Frans Bouma | Lead developer LLBLGen Pro
Puser
User
Posts: 228
Joined: 20-Sep-2012
# Posted on: 25-Feb-2021 09:33:21   

Yes. I tried to be clear as much as possible in my first question.

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39760
Joined: 17-Aug-2003
# Posted on: 25-Feb-2021 16:50:02   

Puser wrote:

Yes. I tried to be clear as much as possible in my first question.

No offense but I took a wild guess of what you wanted as it was totally not clear to me wink

We'll see what we can do, but not in the upcoming version. It's also something we don't like to do, as it could quickly lead to projects 'accidentally' not being generated because they were disabled the last time and someone forgot to re-enable them again. So it's a serious breaking change, usability wise, and we have to think about it.

(edit) A better solution would be to determine if an element in a derived model was changed since the last generation and if so, generate code for that model and not for the other models. And make that optional (disabled by default). But that too has plenty of pitfalls so it's not as simple as it looks. (The entity model is enabled always and that'll likely stay that way)

Frans Bouma | Lead developer LLBLGen Pro