LLBLGen Pro Support System Custom Templates feed

Update 5.3 to 5.9 by Otis

Otis — Wed, 25 Mar 2026 06:50:09 GMT

B wrote:

Using adapter, .net 4.8, & SqlServer22 We have some custom templates and groups that add an intricate security filtering done when loading entities. The templates have references to InheritanceInfoProvider and since this was moved into the ModelInfoProvider . Should I modify the references so to something else or do I need new templates and if so where do I find those?

The previous creators of this have long gone so I am not sure why something were done the way they were.

The API provided by the InheritanceInfoProvider is now exposed by the ModelInfoProvider, so you can replace 'InheritanceInfoProvider' with 'ModelInfoProvider' in your templates. If this doesn't solve your question, please provider a snippet of the code (the template) you're struggling with so we can explain it better in that context.

Also, be sure to read the Migrating your code section of our documentation: https://www.llblgen.com/Documentation/5.13/LLBLGen%20Pro%20RTF/migratingcode.htm especially the sections 5.3->5.4 and up.

Update 5.3 to 5.9 by B Rightmer

B Rightmer — Tue, 24 Mar 2026 23:12:35 GMT

Using adapter, .net 4.8, & SqlServer22 We have some custom templates and groups that add an intricate security filtering done when loading entities. The templates have references to InheritanceInfoProvider and since this was moved into the ModelInfoProvider . Should I modify the references so to something else or do I need new templates and if so where do I find those?

The previous creators of this have long gone so I am not sure why something were done the way they were.

Skip file creation for custom template (lpt) by Otis

Otis — Sat, 14 Mar 2026 07:07:24 GMT

It's probably doable with a setting and a preset file. Define a custom setting for entities, then set that setting to true (or to a value) for the entities you want to include in the template execution, then define in the preset file the specific element selection rule. See: https://www.llblgen.com/Documentation/5.13/SDK/tasksxmlformat.htm#preset-definition-xml-format

So, <elementSelectionRule isEnabled="" settingName="" operator="" operand="" targetElementType=""/> should be able to get you there. So not via attributes but via settings.

An example: <elementSelectionRule isEnabled="true" settingName="OutputType" operator="3" operand="PocoWithLinqQuery,PocoWithQuerySpecQuery" targetElementType="8" /> which selects all typed lists which have the setting 'OutputType' set to either PocoWithLinqQuery or PocoWithQuerySpecQuery. All other typed lists aren't taken into account in that task. See the preset SD.Presets.Adapter.General.preset

Skip file creation for custom template (lpt) by jovball

jovball — Fri, 13 Mar 2026 15:21:51 GMT

I'm working on some lpt templates to generate Facet DTOs. Yes, I see the irony in using a code generator to create something used by a source code generator.

My initial template is looking for a FacetModel attribute on the entity and then at FacetInclude or FacetExclude attributes on the entity fields. If the entity does not have the FacetModel attribute, I end up with an empty cs file. I would prefer to skip that file creation. Is there a way for me to do that?

Write once fields with EF Core by Otis

Otis — Thu, 19 Feb 2026 07:38:18 GMT

Not sure how many fields you need to do, but one way could be to use a partial class of the generated context and implement the partial method OnModelCreatingComplete(ModelBuilder modelBuilder). In there you can use

modelBuilder.Entity<MyEntity>().Property(t=>t.CreatedBy)
    .Metadata.SetAfterSaveBehavior(PropertySaveBehavior.Ignore);

(or a less verbose version, but you got the idea).

You can generate this class too if you want of course, if e.g. there are many fields to apply this to.

Write once fields with EF Core by jovball

jovball — Tue, 17 Feb 2026 21:38:54 GMT

I'm using LLBLGen 5.13. We have some fields that should be write-once. An audit field for CreatedBy is an obvious example but there are other fields that fall into this category too. These fields may not be database generated.

The way to configure that would be in the entity mapping to add ".Metadata.SetAfterSaveBehavior(PropertySaveBehavior.Ignore)" on the field. There are two field examples below with that configuration.

I'm looking for a recommendation on how to emit that code. I'm assuming I will need to use a custom template and I'm doing this for the fields with standard names such as the ones like CreatedBy and Ulid in the example. For non-standard fields, what would the best way to flag those fields for the template? Add an attribute like [WriteOnce]?

protected virtual void MapMyEntity(EntityTypeBuilder<MyEntity> config)
{
    config.ToTable("MyEntity", "dbo");
    config.HasKey(t => t.Id);
    config.Property(t => t.Id).HasColumnName("MyEntityId").ValueGeneratedOnAdd();
    config.Property(t => t.SomeValue).HasMaxLength(200).IsRequired();
    config.Property(t => t.Ulid).HasMaxLength(26).IsRequired().Metadata.SetAfterSaveBehavior(PropertySaveBehavior.Ignore);
    config.Property(t => t.CreatedDateOffset).ValueGeneratedOnAdd();
    config.Property(t => t.CreatedBy).HasMaxLength(100).IsRequired().Metadata.SetAfterSaveBehavior(PropertySaveBehavior.Ignore);
}

Disable taskGroupPreset or taskPreset by Otis

Otis — Tue, 25 Nov 2025 09:25:10 GMT

jovball wrote:

Ignore my last question about performRule. The documentation is here: https://www.llblgen.com/Documentation/5.12/SDK/tasksxmlformat.htm

Thanks. The performRule xml in the docs was indeed wrong, should be isEnabled, it's fixed now. The editor has rudimentary intellisense indeed, on xml and also for C# (e.g. in the search editor).

Disable taskGroupPreset or taskPreset by jovball

jovball — Mon, 24 Nov 2025 19:26:22 GMT

Ignore my last question about performRule. The documentation is here: https://www.llblgen.com/Documentation/5.12/SDK/tasksxmlformat.htm

Disable taskGroupPreset or taskPreset by jovball

jovball — Mon, 24 Nov 2025 13:36:54 GMT

I meant to include this in my original post.

https://www.llblgen.com/Documentation/5.12/SDK/tasksandpresets.htm

TIL: That Edit as XML has Intellisense. I've always thought of it as just a Notepad type editor.

One more question while I'm here. Some of the existing taskPresets have a performRule element but I don't see any documentation on it. What does that do?

<performRule isEnabled="false" settingName="" operator="0" operand="" />

Disable taskGroupPreset or taskPreset by Otis

Otis — Mon, 24 Nov 2025 07:58:32 GMT

The syntax is isEnabled="false", not enabled="false". If you use the preset editor -> Edit as Xml, you get intellisense which will tell you this. Also, e.g. the preset SD.Presets.Adapter.General.preset has 2 disabled tasks at the bottom. I tried it out and disabling a task in the preset using isEnabled="false" worked fine.

So I think the docs are wrong here, so which document mentions this wrongly so we can correct it?