Organizing classes in namespaces as the entity model gets larger

[apolon]

I'm slowing ramping up on the use of Entity Developer and its going well. The number of entities is growing and it would be preferable to organize them into namespaces based on the area of functionality. It would be nice to have the Entity Developer class hieararchy UI be namespace aware but diagrams can be used to group the classes.

The class list below the .hbml file in Visual Studio is starting to get less manageable. Its great that the Entity Developer custom tool provides this functionality but it would be preferable that it had a namespace sub-tree as well. I will add these namespace feature requests to user voice. In the meantime, does anyone have any suggested approaches for handling the organization of large entity models within both the Entity Developer UI and the Visual Studio project system?

FYI: https://devart.uservoice.com/forums/386 ... me-space-i

[Shalex]

We recommend you to split the model into several thematic diagrams: http://blog.devart.com/working-with-lar ... html#split.

[apolon]

Will do, but its not ideal - hence the user voice submission.