.NET partial classes

[Ricardo Guerra]

Hi there,

EA duplicates UserControls partial classes that have a .Designer.cs file when using the Import Source feature. Is there a way to avoid this or to remove them after generation ?

Thanks in advance!

Cheers,
Ricardo

[«Midnight»]

Not in 7.1, and I don't know whether this might changed for 7.5 production (I just have not checked in the beta versions).

At least EA will handle partial classes properly when forward engineering.

Search the forum for a few suggestions on how to work with this paradigm, as well as some of the limitations you must respect.

I know this is not the answer you are hoping for, but it might at least save you some lost time looking for a solution that is not there.

David

[Ricardo Guerra]

Yes, we are using 7.1...

I was thinking to automate the duplicate objects after reverse engineering but that might be error-prone...

By the way i couldnt find anything on the forum related to this subject...

Thanks

[«Midnight»]

You have to dig a bit to find the forum posts, but they exist. Sorry, but I cannot think of any 'exotic' keywords that might narrow the search.

I think you could write an automation tool that would clean things up a bit. Yes, it might be error prone, but only to the extent that you would need to be careful with partial classes when programming (the classes themselves).

There are some other ways to handle this, at least as far as presentation is concerned. Whether EA would handle them gracefully is something you would need to test for yourself. For example, perhaps you could create a composite element - either use one of the partial class components or create a new element - and make it composite. Drag the (remaining) components of the partial class to the 'inner' class diagram. Now you have a neater appearance on the original diagram, while preserving the partial components. As I say, you'd have to test this. I have not tried it myself.

David

[Ricardo Guerra]

Thanks for your reply Midnight!