How to import/link a VS-project properly?

[kodo65]

Hi!

I'm about to embark on a journey where I'm looking at generating an IT-architecture from an existing system on the form "as built". The system is a VS2010-solution consisting of, roughly, 50 projects. My intention is to use the MDG EA/VS plug-in in order to "map" an EA-package to a given VS-project. Ultimately I'd like to be able to map the solution to x-number of EA models, thus using EA to create various "blueprints" in order to create and document an IT-architecture of the system.

Is there any "best practices" on how to carry out this type of reverse engineering effort using EA?

One more thing: in order to test the plug-in, I've tried the plug-in and successfully imported and linked a given VS-project to an EA-package. This works great but there is one thing I'm "missing": the namespace structure that is created is not "drilldownable" - what I mean here is that there are no "package diagrams" generated in EA. It would be great to be able to browse the namespaces by clicking the "namespace package symbol" in a diagram thus "drilling down" on a subsequent level...

Any comments and/or suggestions on the above are very much appreciated:)

Cheers,
/Peter