How to Use ASP.NET Zero Power Tools Without Breaking Multi-Tenancy

ASP.NET Zero Power Tools will build you a page. ASP.NET Zero multi-tenancy will decide who is allowed to see the rows. Those are different jobs. The generator is fast on purpose. Tenancy is slow on purpose. Mixing them is how Tuesday becomes a support thread.

This guide is for license holders and tech leads who just generated an entity and felt a little too proud. You will get what Power Tools actually emits, what you still type, the IMustHaveTenant / ABP data filter rules, a smoke-test table, and when a dedicated development team is cheaper than a leaked tenant.

We do this as a service. You still own the code. Last week’s post was the upgrade merge. This week is the CRUD you generate between upgrades.

Contents

• Key takeaways
• What Power Tools is for (and is not)
• Multi-tenancy is a filter, not a UI checkbox
• Path: generate, then prove Tenant B
• Conflict with DisableFilter
• Smoke-test checklist
• Upgrade vs generate
• Frequently Asked Questions
• Conclusion

Key takeaways

• Power Tools generates entities, DTOs, AppServices, permissions, Angular/MVC/React UI, tests, and more. It does not think about your host-vs-tenant product rules.
• Put IMustHaveTenant (or MayHave) on purpose. Do not assume the template guessed your isolation model.
• ABP data filters apply TenantId for you if the interfaces are right. DisableFilter is a loaded gun.
• Official docs now describe Power Tools as a global .NET tool with a web UI, not only a Visual Studio extension.
• Pretty CRUD is not the test. Tenant B must fail to see Tenant A’s row.

What Power Tools is for (and is not)

ASP.NET Zero Power Tools is a RAD workflow. You define an entity. It generates the boring layers from database to UI. Volosoft’s own pages say it: spend minutes on CRUD, spend your brain on business logic.

Use it for:

• Standard records: customers, orders, tickets, catalogs
• Master-detail that still follows Zero conventions
• Regenerating after you change the entity JSON

Do not use it as:

• A substitute for domain rules
• A way to skip [AbpAuthorize]
• A tenant-isolation strategy

The 2026 global-tool / browser UI upgrade changes how you launch it. It does not change the tenancy physics.

Multi-tenancy is a filter, not a UI checkbox

ABP’s data-filter docs are still the law. If you implement IMustHaveTenant, queries pick up TenantId from IAbpSession. Host versus tenant databases change what DisableFilter can even mean.

Support thread #3028 is the classic scare: host entities visible to tenants, or not, depending on MayHave versus MustHave and whether you merged lists by hand. Thread #2662 is the other scare: reading host data while inside a tenant. The recommended tool is often SetTenantId(), not a casual disable.

ASP.NET Zero CRUD that looks right in the Default tenant is not done.

Path: generate, then prove Tenant B

1. Generate the entity with Power Tools (same project type: Angular, AngularMerged, MVC, React).
2. Open the entity. Confirm IMustHaveTenant or IMayHaveTenant matches the product rule.
3. Confirm the AppService does not disable tenancy filters “to make the grid populate.”
4. Grant permissions per tenant role, not a god host user for demo day.
5. Log in as Tenant A, create a row. Log in as Tenant B, run the same GET. Empty is success.
6. Try one write as Tenant B against an id from Tenant A. It must fail.

That loop is how you use ASP.NET Zero Power Tools for the rest of the product’s life without a silent leak.

Conflict with DisableFilter

You will want to disable filters for a report. Sometimes that is correct. Wrap it in a using, add your own Where, and write a comment that names the threat. In a database-per-tenant world, disable will not magically join host and tenant stores. Believe the docs.

File-scoped namespaces and regenerated UI will fight you on merge days. That is last week’s upgrade post. This week: do not “fix” an empty grid by turning off tenancy.

Smoke-test checklist

Before generate	After generate	After deploy
Host vs tenant data rule written down	Entity interfaces match the rule	Tenant B cannot GET Tenant A
Who may create this entity	Permissions exist on the new page	One forbidden write fails
Power Tools project type matches the repo	No DisableFilter in the happy path	Logs show the acting tenant

Pretty UI is not the test. A compile is not the test.

Upgrade vs generate

Last week: overlay a clean template, merge, conflict table. This week: generate inside the version you are already on. Do not mix a v15 merge and a 40-entity Power Tools binge in the same panic sprint.

We will not quote a fake “two-day CRUD for every module.” Size depends on relationships and tenancy edge cases.

Frequently Asked Questions

How do you use ASP.NET Zero Power Tools in one sentence?

Define the entity, generate, then prove Tenant B cannot see Tenant A.

Does Power Tools set IMustHaveTenant for me?

Check. Do not assume. Your product rule might be MayHave, host-only, or something uglier.

Can we jump to DisableFilter to speed a demo?

Not in production. A demo that skips the filter trains the leak.

Do we need a dedicated development team?

Not always. Someone who has been burned by ABP filters, plus your people who know the domain, beats a generalist who has never seen a tenant.

Is this the same as Angular vs MVC?

Power Tools supports multiple UIs. Tenancy lives on the server. Pick the UI you already run.

Conclusion

ASP.NET Zero Power Tools is how you stop typing boilerplate. ASP.NET Zero multi-tenancy is how you keep Tuesday from becoming an incident. Generate. Then log in as the other tenant.

If you want help, that is dedicated-team and framework work we already sell (including Code Migration). If you want to do it in-house, paste the smoke-test table into the ticket. Either way, stop treating an empty grid as a reason to disable the filter.

Sources: ASP.NET Zero, Power Tools overview accessed 2026-09-07; ABP, Data filters accessed 2026-09-07; ASP.NET Zero Support, IMayHaveTenant #3028 accessed 2026-09-07; ASP.NET Zero Support, Host data in tenant #2662 accessed 2026-09-07.