Executables in between patches and another query

I've been using wyBuild now for the last year with our product and on the whole it works really well. Very happy with the purchase. Out product forces an autoupdate check on starting up and downloads the patch on the background. When the user restarts the app, it installs the patch

There are 2 questions I have though

1. Executables/ScriptsOne issue did come up recently though and I need some clarification on is regards to running scripts.

Let's say I have version 2.0.3.5.Version 2.0.3.6 has an executable/script which swaps over a database and updates a xml file with some informationVersion 2.0.3.7 is a hot fix for some issues which came up. It contains no executable.

For Users who updated from 2.0.3.5 to 2.0.3.7 the executable/script didn't appear to run. The above scenario only worked if users went from 2.0.3.5 to 2.0.3.6 then from 2.0.3.6 to 2.0.3.7.

I set it to run the executable after the patch. Am I doing anything wrong on my side?

2. ManifestsI'm getting a little confused as to how msi works with wyBuild. I want to avoid the message which asks for the original msi file or removes files which is required. Lets say I have the following

a.dll <----Installed from the original msi file and in the 1st file list.b.dll <-----Added to a subsequent build but not in the original msic.ini <-----Changing the value in an ini file and in the msi but not in the 1st file list for wyBuild.

Scenario 1 for a.dllI don't include reference to this dll in a patch update. After the patch, I'll be asked to locate the original msi file to get this dll as it will be removed after the patch update. This I get.

Scenario 2 for b.dllI remove reference to this dll in a patch update. It's not in the original msi or 1st file list for wyBuild. Will I be asked to locate the msi after an update?

Scenario 3 for c.iniI add this file to change a value after a patch update but only want it for that specific update. If I don't include it in subsequent file lists, will it be removed?

At the moment I'm keeping b.dll and c.ini in each patch for fear that if I don't then they'll be removed in subsequent patches. This way my patch list if getting bigger and bigger with some unneeded files.

Would be grateful for any advice anyone has on this

Yours

Raza

I set it to run the executable after the patch. Am I doing anything wrong on my side?

This was a bug fixed in wyBuild 2.6.16. Update to the latest wyBuild and rebuild your updates.

I'm getting a little confused as to how msi works with wyBuild. I want to avoid the message which asks for the original msi file or removes files which is required. Lets say I have the following

The problem is "advertised shortcuts" that the MSI makes. Make sure your MSI makes plain old vanilla shortcuts. See: Advertised shortcuts in the installers... how avoid it.

Scenario 3 for c.iniI add this file to change a value after a patch update but only want it for that specific update. If I don't include it in subsequent file lists, will it be removed?

I'm not quite sure what you're asking. You need to add *all* files to wyBuild. Let wyBuild decide which files to add, which to delete, and which to patch.

Thank you for your reply.

It's good to know issue 1 is now resolved.

Re issue 2. I understand now around how to avoid in the MSI set up from now on. The problem I have is all of my sites have already had MSI builds with normal shortcuts and it will be difficult to undo this. Thank you for clearing things up for me.

Really happy with our patching process otherwise using wyBuild.

Keep up the good work!

Raza

Reply
Discard post