Irradiate Startup Behaviour In VS2008 And GC?

If VB5/6 could read Unicode I would remain in it for ever as it is to me the most efficient way of getting all things done, and I have likely done more in VB classic than most care to try on VS.NET Now, in the midst of trying this system I keep a red light lit in the back of my head, on constant alert due to the GC part of .NET.

No matter what I read, I just get more precarious about the implementation of a Garbage Collector in VB, as this means I cannot absolutely say that a username and password is cleared from memory when I want to.In spite of tallking directly to Mr Bjarne Stostrup (the inventor of C++) and reading two ebooks of a few hundred pages each over the past night, some things still boggles the mind.

Such as...Why in heavens name does the MSDN library opener say "Help is updating to reflect your recent changes. This may take several minutes"Well its not so bad if it happend once, as on the installation of the MSDN disks, but when it happens EVERY TIME that I open MSDN or VS2008, that makes me wonder.Especially when I just closed VS2008 and opened it again five minutes later.

The latest "update" according to the MSDN opener took not only a few minutes but approx. 20 minutes, although I did nothing to change anything since the last time I opened it.Is there any way to disable this constant updating of nothing?

Once more back to the GC issues.Does anyone have a simple to use class, so that at my will I can issue a simple call to a method to clear anything and everything unused from the GC box, short of having to close my application and reopening it?I mean, would it be to much to ask for a simple command that allows us to do this, without having to "imrpove on the MS developers years of efforts" by our own non standardized methods?

What I would like to see implemented in VS.NET would be a simple thing for the boys and girls at Mr. Gates command, to add the following

....GC.ClearAllDead

When called, it guarantees to clean the GC, empty all unused addresses and simply Dispose and Finalize everything at our will, and not leave this sometimes time and security critical part to the will of a users sometimes slow and willful PC.

Everyone knows how easy it is, and common to date that you load a webpage with some flash or adobe files and your computer starts sounding like a spaceship ready for relaunch.Quite obviously, something is running up your CPU and memory usage, and doing things you did not ask it to do when going to read your blog pages for example.Often I have experienced this, and still do on a daily basis, and I sweat every time I think of the possibility any application starts accessing memory addresses to scope up whatever junk is left in memory.Coupled with Garbage Collection potentially leaving items in memory addresses until it wants to free this itself.Now what if someone sneaks a trojan of a new variant onto your system, and this constantly sniffs your RAM for new funny and useful code.

there went your UID/PWD combo to both online banking, blogs, GMAIL, hotmail and all other nice things you use. Consider yourself facebooked in a nasty way, and then tell me GC is all good and poses no risks.So, the addition of the simple GC cleaner above would have been, and should have been, in my oppinion, the first and foremost update to the .NET package before it even was released, thus making it easier and faster for new and old programmers to avoid this cause for (perhaps to be considered as) paranoia.With my background from security and time critical related work, I would still prefer to patch the holes before they become an issue, and I will continue to chose being paranoid and safe rather than leaving this potential hole open.