Hi All
We have been using Installshield Express 3.5 for several years now to both install and upgrade our apps - works well. We have just upgraded to Visual Foxpro 9 which comes with the Limited Edition of Express 5 and now when we build an upgrade project and run it...
It deletes all existing files in the app folder before copying the new files. As our apps have been out there for several years we cannot guarantee what previous version is running on the client machine. We cannot therefore dictate msi unique IDs.
We just want it to work like v3.5 - copy all the files into the INSTALLDIR
HELP !!
Any thoughts as this is now delaying new release
Thanks in advance
Springbox
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Installshield Express destroys app
Started by
springbox
, Sep 11 2006 23:44
2 replies to this topic
springbox
-
- Members
- 3 posts
Posted 18 September 2006 - 11:10
Well Installshield are struggling with this one. They say they have never come accross this one before - mmm - not sure we believe that.
There are clearly problems with file versioning rules here.
How do we leave the user's data intact when we do an upgrade? (patching will not allow us to change redistributables, so that is not an option).
Come on guys - no thoughts ?
Springbox
There are clearly problems with file versioning rules here.
How do we leave the user's data intact when we do an upgrade? (patching will not allow us to change redistributables, so that is not an option).
Come on guys - no thoughts ?
Springbox
springbox
-
- Members
- 3 posts
Posted 22 September 2006 - 10:22
Hi Guys
At last sorted it out.
You are not going to believe this one...
The wierd behaviour was caused by the merge module MSXML3 - with it disaster, without it - perfect.
Both Wise and Installshield projects produce this wierd behaviour so it is obviously a MS Installer bug / conflict.
I just hope we can get on with either a later version of the same file or MSXML4 instead.
We have spent several days of midnight plus finishes pratting about with this one. We thought it was us but tech support at Installshied can reproduce the same behaviour with our project.
Thanks for everyon'e input .........
SpringBox
At last sorted it out.
You are not going to believe this one...
The wierd behaviour was caused by the merge module MSXML3 - with it disaster, without it - perfect.
Both Wise and Installshield projects produce this wierd behaviour so it is obviously a MS Installer bug / conflict.
I just hope we can get on with either a later version of the same file or MSXML4 instead.
We have spent several days of midnight plus finishes pratting about with this one. We thought it was us but tech support at Installshied can reproduce the same behaviour with our project.
Thanks for everyon'e input .........
SpringBox