Can you please give us more details about this? Is it a Windows Installer based setup?
Basically no. What I mean is that, once the application has been installed on a central location, any client can access it without installing anything on the local machine. My deployment is more complex than that but, for the purpose of the installer, it is similar to simply deploying an exe file with no required modification at all to the registry or anything else. All that is actually required for running the application is have access to the exe file and launching it.
However, I don't understand what the problem is with the update process. Since the application is installed locally, on each user machine, why there is a problem when you "update" the application on the server?
Ok, I'll try to explain both the architecture and the issue more clearly. Sorry if it's a bit long. Let me know if this isn't clear:
Basic architecture
MyApplication.exe is made of many different executable modules (other exe files) that implements various features. All of these modules depends on several shared libraries (DLLs and BPLs) that are loaded immediately when a module starts and only released when the module exits.
How it is deployed in the problematic scenario
In this case, here is the typical deployment:
- The network admin creates a network share to host the application (call it \\srv\application1)
- The network admin runs the installer from a random client system (or directly from the server) and specify \\srv\application1 as the application's installation location ([APPDIR]).
- Users will simply invoke \\srv\application1\MyApplication.exe to start the application.
How the problem occures
- An admin receives an update for the application. He may or may not be using the same system as the one he initially used for deployment (that is typically the case when several users are "managing" the application).
- At the same time, other users are using the application. The admin request them to go out but they might not actually follow the instructions (this is, sadly, very common) and that could leave some application running. Let's imagine, for instance, that one user has left the "MyApplicationDashboard.exe" executable running. That application locks the shared library files but does not mock the main executable (MyApplication.exe).
- The admin, believing everyone is out of the system, initiates a deployment. The installer will prompt for a destination and he will select \\srv\application1.
- The isntaller will perform its preinstallation cehcks: no files in \\srv\application1 is locked from the admin's system and neither is any of the application's executable running on it. The installer then (incorrectly) assumes that the installation can safely be performed and starts copying files.
- Since I couldn't specify the other in which the various files are deployed, the installer will do that more or less randomly. Statistically, it will deploy several executable modules before reaching either "MyApplicationDashboard.exe" or one of the shared libraries.
- When the installer finally reachs one of these files, it encounters a shared access denied error and will prompt the administrator for instructions.
- If the admin goes to each user and terminates the still running applications (all of them) before returning to the installer and click "try again", all is well.
- If the admin does NOT do that, however, the result is always a half-broken installation: all executables that already have been deployed will fail to start because the shared libraries are not the ones they where compiled for.
I know it seems like a far-stretched scenario but it is, in fact, one we experience frequently: a lot of our customers are small to medium financial firms with little or no proper IT support. One of the reason they chose our system is that it is trivially easy for users to deploy and maintain it themselves with little or no external IT help. The typical user of the application it not very proficient with computers and technology but quite focus on their core business. Many will fail to follow simple instructions and that results if frequent deployment issues similar to what I'm describing. The problem is made worse by the fact that we do release new version quite often.
I will resend the email containing my project to the same address, placing the link to this thread in the subject for easy identification.
Thank you for your help,
regards,
Stephane
FOLLOW US
Get the latest news in Application Packaging