So it is often best for an installer to be simple and always work, even if it leads to a few more restarts for the user. Testing installers takes a long time, as you need to try to guess every state a user’s machine may be in. Most self updating applications do this – this should be the norm for mass market applications when there are lot of users.Īll of the above can lead to complex logic that is hard to test. This can only be done if the DLL is used by a single application. ![]() However that make the installer’s UI more complex and leads to more support calls.Īn installer for an application can also get the application to save its state, shut it’s self down, then restart after the DLL has been updated. Some better installers will tell you the applications that should be closed down before running the installer, so letting the DLL be updated without a restart. (Think of the problems if it was not locked!)Ī DLL that is locked cannot be updated, so the installer will ask windows to replace the DLL with the new version the next time the machine is restarted. Therefore the DLL will be locked on disk. If the DLL is being used by an running application, part of it will be loaded into memory and the rest will be read from disk when it is needed. (This much more likely to be the case when upgrading an application you already have installed.) ![]() Often when you install new software a DLL (file) that is used by lots of other software packages need to be upgraded to a new version.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |