Home/ Questions/Q 6122449
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T15:54:01+00:00

OK, This is probably not simple but I figured I would throw it out

  • 0

OK,

This is probably not simple but I figured I would throw it out there:

I get the idea of extending an Model-First entity in EF with a partial class to add data annotation elements somthing like this:

[Required]
string MyString {get;set;}

However, if I am in a multi-tenant system where I may want to customize which fields are actually required when passed to the end client can I dynamically set the annotation depending on how the client has configured the setting, say in another table for instance?

Update: In the multi-tenant system there are at least two databases. One that stores system configuration information. In addition each customer would have their own individual database. The system DB controls routing and selecting the proper customer database from there.

Any insights or ideas anyone has on how to accomplish this would be great!

Thanks,
Brent

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If you are using EF 4.1, you could create different DbContexts, referencing the same entities, but provide different mappings using the Fluent Api.

    Here is a link to a video that describes using the api.
    Fluent Api

    Note: Your database would need to be setup to accommodate all the different configurations. For example, if in one context, “FirstName” is required, and in another it is not, your db should allow NULL in order to cope with both situations.

    • 0