![]() Examples on techniques for eliminating this at application level can be found in MSDN Article “Avoiding DLL Hell” īut if the app has a problem, you don’t have app virtualization as an option, and there is no fix from software provider available…a bit of ProcMon and file copies are probably all you need to fix it. However even without app virtualization on modern Windows such issues are rare and with good application design can be completely eliminated. Today you can use application virtualization technologies such as ThinApp or App-V to eliminate these issues. When DLL conflicts occurred it was called ‘DLL HELL’ mostly because finding the root cause of such problems was a hellish experience. It was critical to install all apps, service packs, option packs in very specific orders to get a reliable system. ![]() In Windows NT 4.0 DLL hell was a common occurrence. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |