shoda
01-26-2008, 06:14 PM
I have an application that is currently using TrueUpdate version 1 and I am trying to update it to version 3. We update our programs doing a complete install (the same program installs our software completely or updates to a new version). Therefore the TrueUpdate exe file and dat files are being replaced. In version 1 of TrueUpdate, we have been getting a data move error during this process which I think is due to the fact it is trying to replace an open file. We are hoping that this new version 3 will solve this problem.
I created a new TrueUpdate project to replace the old version (I used the wizard to create my code). I customized it a bit and it seems to work fine exept for the following problem.
- I run the TrueUpdate v3 program. It finds an update to my application and installs in correctly
- During the installation, the update v3 program is overwritten by the old v1 version because I haven't embedded the new update program into a release yet. (I am still testing)
- Instead of the v3 update program re-opening after the upgrade of my application and showing the "SUCCESS" screen, it stays closed and is not visible on Task Manager.
Is this due to the fact that the TrueUpdate (v3) application is being overwritten by the TrueUpdate (v1) application or could I have another bug in my routine.
Hope that
I created a new TrueUpdate project to replace the old version (I used the wizard to create my code). I customized it a bit and it seems to work fine exept for the following problem.
- I run the TrueUpdate v3 program. It finds an update to my application and installs in correctly
- During the installation, the update v3 program is overwritten by the old v1 version because I haven't embedded the new update program into a release yet. (I am still testing)
- Instead of the v3 update program re-opening after the upgrade of my application and showing the "SUCCESS" screen, it stays closed and is not visible on Task Manager.
Is this due to the fact that the TrueUpdate (v3) application is being overwritten by the TrueUpdate (v1) application or could I have another bug in my routine.
Hope that