DLL Management, that is the ultimate goal, right? If you could tell all the developers in the world what they can and can't use, when files had to be updated, where they would be stored? Seems too good to be true, right? Well, Microsoft has come up with their version f a solution. The solution is System File Protection.
The Windows 2000 Operating System features System File Protection. Programs that are being installed will load their own systems files into their own directory. It will also overwrite the files with the same name in the Windows directory. After the installation is complete, the replaced files will be returned to their original state. This is done to avoid system and file conflicts. Microsoft has stated that they will be updating their DLL library, so there should be no problem with programs that will need the new DLL's.
They will perform this in much the same manner as the anti-virus folks update their virus definition files. This sounds great, but will be difficult and cumbersome.
Today, Microsoft ran into a snag in their managed DLL system. Two files, rsaenh.dll and schannel.dll caused some problems with the 128 bit encryption of IE 5.0 on Windows 2000. In fact, they halted it's functionality, leaving users with the message:
"System cannot log you on because domain Computername is not available"
For this full story, see the following link: http://www.zdnet.com/zdnn/stories/news/0,4586,2462008,00.html?chkpt=zdnntop
Managed DLL's sound like the greatest thing since the Window first appeared, but who knows it viability. I guess that only time (and a whole lot of bug fixes) will tell.