File version gets deleted from file table on save
Hello all...
So...I am creating a small update to an app, a couple of new files, and when I add the new files in, which have a higher version number than the old version of the file, the new version number shows up in the file table and all appears to be well.
I then save/compile the wsi, using Wise Package Studio SP3, and the file version has been stripped from the file table only for 2 of the updated files.
Well...I am deploying this update via msiexec /fvomus <UPDATEDMSINAME>.msi /qb-! and, what do you know, the 2 files that had their version stripped are not there....the old versions are still there.
I have tried removing, saving, readding, saving several times now and each time the file version is getting wiped out on save.
Anyone ever seen this before?
So...I am creating a small update to an app, a couple of new files, and when I add the new files in, which have a higher version number than the old version of the file, the new version number shows up in the file table and all appears to be well.
I then save/compile the wsi, using Wise Package Studio SP3, and the file version has been stripped from the file table only for 2 of the updated files.
Well...I am deploying this update via msiexec /fvomus <UPDATEDMSINAME>.msi /qb-! and, what do you know, the 2 files that had their version stripped are not there....the old versions are still there.
I have tried removing, saving, readding, saving several times now and each time the file version is getting wiped out on save.
Anyone ever seen this before?
0 Comments
[ + ] Show comments
Answers (8)
Please log in to answer
Posted by:
dj_xest
14 years ago
Looks weird... Can you try dragging those two files from the source to the destination folder again using the Installation Expert then save and recompile? I have seen this before but I was able to fix it after doing that.
The other way around is once you have temporarily removed them from your project, also check and remove other traces in other tables like WiseSourcePath by searching the tables.
Then add those two files again, save and recompile.
BTW, where is the destination of those files?
The other way around is once you have temporarily removed them from your project, also check and remove other traces in other tables like WiseSourcePath by searching the tables.
Then add those two files again, save and recompile.
BTW, where is the destination of those files?
Posted by:
happyphunn
14 years ago
I got tired of trying to figure out why it was getting wiped out and actually noticed in the previous msi I made...the file version got wiped out there too.
I just added those two files to the remove file table so they get removed during reinstall and then when a user launches the advertised shortcut the app self-heals and puts the right versions down. It would need to self-heal anyway as I am added current user registry info to it and deploying to allusers via the system account sooo....
Weird though right....
I mean....there were no traces of those files in any table after I removed them. I then saved and compiled the wsi without the files there. Then I went back and added them and recompiled...still no luck.
The files were in a subdirectory in Program Files...
I just added those two files to the remove file table so they get removed during reinstall and then when a user launches the advertised shortcut the app self-heals and puts the right versions down. It would need to self-heal anyway as I am added current user registry info to it and deploying to allusers via the system account sooo....
Weird though right....
I mean....there were no traces of those files in any table after I removed them. I then saved and compiled the wsi without the files there. Then I went back and added them and recompiled...still no luck.
The files were in a subdirectory in Program Files...
Posted by:
anonymous_9363
14 years ago
FWIW, log a call with Symantec. They'll ask you to send the files (all versions) and the WSI. Bear in mind that Wise appears to be so low on Symantec's radar that it's practially invisible. Take it from me: if it's a bug, you'll be dead before it even hits the "To do" list...
Posted by:
happyphunn
14 years ago
ha....nice!!!
So...should I NOT be trying to get management to renew our WPS licensing and upgrade to Enterprise Management Server?
So...should I NOT be trying to get management to renew our WPS licensing and upgrade to Enterprise Management Server?
Posted by:
anonymous_9363
14 years ago
Let me put it this way. From information I have received, opinions expressed here on AD and from reviewing posts on Symantec's Connect, I have strongly advised the client I'm currently working for to consider a move to InstallShield. As a freelancer, I won't be wasting any of my own time in pursuing Wise technologies with which I'm not already familiar.
Posted by:
nheim
14 years ago
Hi Andrew,
had this a few times too in the past. Every time, it was an incorrect version resource!
So, please check the version resource of files in question carefully.
Regards, Nick
had this a few times too in the past. Every time, it was an incorrect version resource!
So, please check the version resource of files in question carefully.
Regards, Nick
Posted by:
happyphunn
14 years ago
What does that mean..."incorrect version resource"?
Does that mean that the actual source file has an invalid version on it....
Thanks.
Does that mean that the actual source file has an invalid version on it....
Thanks.
Posted by:
nheim
14 years ago
Hi Andrew,
that means, that the version checking does only work, if the files to install have a correct version info in their resource.
If you have access to the source code of this files, have a look at it.
If not, use Resource Hacker or any other Resource tweaking tool, to control the version info.
Regards, Nick
that means, that the version checking does only work, if the files to install have a correct version info in their resource.
If you have access to the source code of this files, have a look at it.
If not, use Resource Hacker or any other Resource tweaking tool, to control the version info.
Regards, Nick
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.