>I used to micromanage my registry, back when it was consuming valueable >space in the paged pool... as of XP, the registry is mapped in chunks, >just like any other file (or database, for that matter). > >http://support.microsoft.com/default.aspx?scid=292726 > >These days, I don't notice regclean-esque tools adding any perf to my >system. If I were you, I wouldn't worry about it anymore, unless you're >really in the regular habit of registering COM objects and then deleting >their implementations... like, numbering in the thousands.
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. - Andy =================================== 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
