Sharing tables/models across LINQ database model

Question

I am not sure of the exact terminologies involved so please bear with me.

I have an ASP.NET MVC website - my first go at using this - and I decided to spread the Database Model (dbml file in other words) across 2 logical mappings. I thought they were logical until I decided to include my "Tags" table in both of the dbml files. This now makes the generate code duplicate a "Tags" class and therefore will not permit me to compile.

The obvious way round this is to get rid of my logical split across the 2 models and just whack all the tables and their relationships into a giant dbml file. This is what I will do if I cannot find a simple solution.

Does anyone have a solution to this probably common issue? Is it a simple case of inheriting one model from another making the various model/entities available everywhere?

Thanks in advance, mo

Answer 1

I guess, technically, you can create them 2 different dbmls and remove duplicates from ones code, but you'll have to do it everytime you change your model. would be kinda creepy.