By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,671 Members | 1,568 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,671 IT Pros & Developers. It's quick & easy.

Namespace mapper utility

P: n/a
Does anyone know if a utility available that can iterate through all the assemblies in a project and build a single map of your namespace? What I need is something like the class view in VS.NET except that I need it for the entire solution and not broken down by individual assemblies? I know that I can use reflection to build this pretty easily, but I'm hoping that someone has already build a robust solution for this

Thanks

Ian
Nov 15 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Can you take a look at
http://www.windowsforms.net/Terrariu...se.(none).aspx
and let me know what you think of that object model presentation.

I wrote that about 2 years ago, and I could probably dig up the code.
--
Justin Rogers
DigiTec Web Consultants, LLC.
Blog: http://weblogs.asp.net/justin_rogers

"R. Ian Lee" <an*******@discussions.microsoft.com> wrote in message
news:3B**********************************@microsof t.com...
Does anyone know if a utility available that can iterate through all the assemblies in a project and build a single map of your namespace? What I need
is something like the class view in VS.NET except that I need it for the entire
solution and not broken down by individual assemblies? I know that I can use
reflection to build this pretty easily, but I'm hoping that someone has already
build a robust solution for this.
Thanks!

Ian

Nov 15 '05 #2

P: n/a
Justin

Thanks, but that's not quite what I'm looking for. I need something that resembles the Class View in Visual Studio except that at the top of the tree, it would have the solution instead of the component. Something like..

[My Big Multi-Component Solution
{} MyCompan
{} We
* SomeBaseClas
* AnotherBaseClassFromADifferentComponen
{} U
* MyUIHelperClassFromComponent
* MyUIHelperClassFromComponent

You get the point... Someone must have written something like this. Surely, people aren't manually verifying that programmers are remembering to put everything in place according to the designed framework? Well, actually they are (I'm one of them) but it seems like a real waste of time when such a utility would make it so easy to verify

Well, if I don't get a response pretty soon I guess I'll have to spit one out... :

Thanks

Ian
Nov 15 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.