Update to specific version

What is the best way to limit what version I want a specific client to update to?

Let's say I have version 1.1, 1.2, 2.0

The client has 1.1 and I want them to only upgrade to 1.2

Should I use the "How to prevent or limit updates" article to do this?

Maybe I can pass in the version number in the %urlargs% variable I want them to upgrade to then pick the upgrade file to return based on that info. Does that sound right?

Would prefer not to have info about the client (i.e. a license key that correlates to the correct version). I can if I need to though...

---------------------

I know this may not sound like the best solution but the reason for this is that this is a client server implementation and the client needs to only update to what version the server is at. The server would also use wyUpdate but updates will be initiated by the administrator at there discretion.

Currently I am hosting all updates to both the server and client on my website.

I guess another option may be to let the server download the update info and then change the location to where updates are picked up from to that location. Not sure if that would work though and sounds more complicated.

Also, for the initial install I am using click-once, not a traditional setup.exe/msi installer. So the very first time someone installs they use click-once, then all subsequent updates are controlled via wyBuild since click-once is not as controllable.

We get questions like this (or tangentially related) pretty frequently. So much so that we're considering making this much easier.

In the meantime the way to do this (as of wyBuild 2.6.18) is to deliver the appropriate wyserver.wys file to the user depending on what version you want them to have. This means 2 things. First it means you'll have to keep all your old updates on your sever. And it also means you have to programmatically deliver the *.wys file the customer wants.

You can use the example code in the Limit updates article to learn how to deliver the version the customer needs based on inputs.

Tell me if this helps.

Also, for the initial install I am using click-once, not a traditional setup.exe/msi installer. So the very first time someone installs they use click-once, then all subsequent updates are controlled via wyBuild since click-once is not as controllable.

Is there any reason in particular you're using ClickOnce for the initial install? I ask because we're releasing installer-building functionality in wyBuild 2.7.0 and we don't want to miss anything crucial.

Sam, thanks for the response. Wanted to make sure I was on the right track.

Would be great if the client could request a specific version out of the box. Looking forward to that.

The main reason we are using click-once is simplicity and it because of auto-updates. So we may move away from click-once in the future since WyBuild will take care of the updates and may even take care of the installer in the future. The main feature that click-once does not have is installer actions, but the main reason for using them is simplicity in deployment for the end user. Just click a link and it installs; no download, extract, and runing an exe.

Thanks.

Sam, any idea on when the installer with 2.7 will be released? I am looking at buying a different installer soon but would rather give yours a try if it will be available in some form or another soon.

Hey Rich,

We're still a bit more than a month away on that. However, when wyBuild 2.7 is released, the install functionality will be based upon Inno Setup. We'll make it easier, of course, but Inno Setup is fairly easy to use right now.

They have active newsgroups (to ask for help if you need it), extensive help documentation, and quite a few examples included within Inno Setup.

Reply
Discard post