wyUpdate deletes exe! [Solved]

[chev]

Hi,

I have a small exe that calls wyUpdate.exe. After the update, I include a bat file in my temp folder to open up my main exe.

When I change my main exe and upload it, wyUpdate replaces it with the old one just fine on opening. However, in my next build, if I DON'T include the exe again, it is then REMOVED from my program's folder?!

Is this a bug or am I doing something wrong?

I assumed that wyBuild only replaced files with the same name but never deleted old files.

Help please!

[chev]

Oh my goodness - I think I may have been an idiot here.

Am I meant to include EVERY file in EVERY version of my app every time I make a change?

I was hoping that I could upload only those files that changed - as it takes a very long time to upload everything to our FTP server.

I hope i'm wrong otherwise I could have continued using our old product

[Wyatt]

Am I meant to include EVERY file in EVERY version of my app every time I make a change?

Yes, but wyBuild does the hard work of comparing your versions and generating the tiny patch files.

So, yes, add every files from every version to wyBuild and let wyBuild do the hard work of comparing the versions.


Does that make sense?

[chev]

Yes thank you!

I've got a bunch of DLL's that I'll never change - which I have NOT included in my update. If I understand you correctly, this should be fine to never include since I'll never need to update them and they were included in my initial installation. (So exist on the client's pc already). wyUpdate will never delete these since they aren't in any previous version right?

So I have another 2 questions:
I haven't included my report files. (They're huge so it takes forever to upload them and seldom change.) If I need to add a report, is it OK if I add it in one version (thereby adding it to the client folder in the update) and then, when doing the next version I REMOVE it from the previous version, thereby "tricking" wyUpdate into thinking that its not actually on my client machine and preventing it from being deleted as well as not having to include it again in the new version. (Hope i'm making sense!?)

Then, if I ever need to change a report, can I simply include it (for the first time) in a new version? (Will that then replace the file with the same name on the client machine? - I'm not worried about this not being able to create a patch - happy for it to simply overwrite the file with the same name on the client.) I would then remove it from wyUpdate and not include it in the next version thereby preventing it from being deleted as well as not having to include it again in a new version.

Gosh thanks for all your help! Hope you can make sense of the above!

[Sam]

I haven't included my report files. (They're huge so it takes forever to upload them and seldom change.) If I need to add a report, is it OK if I add it in one version (thereby adding it to the client folder in the update) and then, when doing the next version I REMOVE it from the previous version, thereby "tricking" wyUpdate into thinking that its not actually on my client machine and preventing it from being deleted as well as not having to include it again in the new version. (Hope i'm making sense!?)

You can do that, but I'm not sure why you'd want to. As Wyatt said, wyBuild does the hard work of comparing your versions. So even if the report files are huge, I'm sure you only make minor changes to the files. In which case wyBuild would generate tiny patches for the files.

Also, if you want to reduce the size of your updates then go into wyBuild, click File -> Properties -> Update & server files, then increase the compression amount (both sliders), and also uncheck "Create a catch-all update for corrupt installations".

[chev]

"You can do that, but I'm not sure why you'd want to. As Wyatt said, wyBuild does the hard work of comparing your versions. So even if the report files are huge, I'm sure you only make minor changes to the files. In which case wyBuild would generate tiny patches for the files."

The only reason I'd want to do this is to reduce the time it takes to upload files to our FTP server. It's taking a very long time and we work in such an environment that if I need a critical update to take place, it must take effect as soon as possible. Right now, our users have to wait between 45-60 minutes to receive critical changes which is unacceptable in our environment.

Does this make sense? Or am I complicating things for myself? Perhaps there is a better way to go about this?

I will give the compression settings a go - will this require a new client.wyc to be deployed? (Or is it merely a setting to compress the files going up to the FTP server?)

Thanks again for all the help.

[Sam]

If you disable the "catch-all update" as I decribed in the post that will reduce the amount of time it takes to upload updates.