More than one type with same name
Reported by Jon Fuller | March 31st, 2009 @ 07:49 PM
I'm having an issue where I've got more than one type with the same name in my assembly.
e.g. Domain.User DTO.User
The problem arises in the TypeGenerator.Add method when we're processing the second of the two. The "matchedAssociations" finds an existing key and moves on, rather than adding the second one appropriately. After this happens, members from the second (DTO.User) start getting added to the first (Domain.User) and things start to break.
Looks like the identifiers used as the key of the "matchedAssociations" needs more resolution than the type name (e.g. User) to include the full name (e.g. Domain.User or DTO.User).
I'll look into it more tonight, and may be able to provide a patch.
Comments and changes to this ticket
-
Jon Fuller April 1st, 2009 @ 03:02 AM
After some further investigation, and a little tweaking I got it to work, but managed to break several tests in the process. I can't tell if the tests should be changed, or if my change is a breaking change. Either way, please find attached a diff with my change and a test.
-
James Gregory April 20th, 2009 @ 11:47 AM
Great, thanks for reporting this (and the patches). I've been out of town so haven't been monitoring tickets, I'll investigate these as soon as possible.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Simple documentation done simply
James Gregory