> It's not a matter of performance, it just that the obsolete > COM registry entries clutters up my view of what the system > is actually using. If you are in development mode of a .NET > component that exposes a COM interface, and you are > recompiling and running regasm repeatedly, it leaves all the > old orphaned COM registry info junk behind. If you then use > Oleview to look at your components, there are gobs of unused > and orphaned entries under the ".NET components" category. > That is what I'd like to get rid of, and I don't know any > painless way to do it. > > It seems that any cleaning tool would have to be .NET aware. > Oleclean isn't, and I suspect that regclean isn't either. > Besides, regclean can have other adverse side effects. I've > discovered that the hard way.
A tool would certainly have to be .NET aware, and would probably get it wrong. This is because the COM entries all point to a valid and present DLL (supplied by the .NET framework) The actual file used is context sensitive; the dll assembly that .NET finds can be dependant on the application requesting the object (ie if the GAC is not hosting it) I would say that the easiest solution to it is to use the appropriate attributes (*) to force the use of the same ProgID, GUIDs, etc Then you have nothing to clean (IIRC) Merak (*) - ProgIdAttribute, GuidAttribute, ClassInterfaceAttribute, etc =================================== This list is hosted by DevelopMentor� http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 26 Jan 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
