Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How to fix type names conflicts in Dynamic Data

We're working in a Dynamic Data project that will handle entities coming from two different namespaces: myModel.Abby and myModel.Ben.

whose classes are:


Abby

myModel.Abby.Car

myModel.Abby.Lollipop

Ben

myModel.Ben.Car

myModel.Ben.Apple

So myModel.Abby.Car and myModel.Ben.Car are homonym. when I try to register both ObjectContext's, an exception is thrown telling us that there are type name conflicts between the mentioned classes (although the types belong to different namespaces).

How can we overcome type-name conflicts, caused by repeated type names among different namespaces?

like image 374
SDReyes Avatar asked Feb 02 '26 04:02

SDReyes


1 Answers

I don't think there is a way around this.

DynamicData routes to the correct forms based on type names. Look in the URL, the type name is always up there someplace. How can DD know which type you mean to interact with?

like image 139
John Farrell Avatar answered Feb 03 '26 20:02

John Farrell



Donate For Us

If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!