Solving Multiple Update Paths

Hello again!

I was wondering how to handle multiple update paths for the system we are building with WyUpdate (thanks for the new version, btw, the S3 upload is awesome 😀). We have a few different branches which could be created and I was just wondering what the best way to handle those was:

1) We have both a 32 and 64 bit version of our product. I think the best way to handle this is to have separate WyBuild Projects.2) We have a few different testing environments to work with: Closed Beta and Public. I thought that this could be handled via having multiple .wyc files, but I have seen no where on how to select the .wyc file within a windows service (running via .NET) in the tutorials or on the forum, so any link or information would be great.3) Lastly, we want to have it so that the public environment is done via a few things, we would allow people to download 'internal versions' (i.e. Greek letters), and release candidates if they so choose, but also have it so that they can just download the stable (or unmarked) versions as well. Is there a way to do that via code (again, utilizing the .NET framework from a service).

You guys were able to help so much last time, so I look forward to seeing what the correct way to utilize these new tools is.

Thanks

thanks for the new version, btw, the S3 upload is awesome 😀

Our pleasure.

1) We have both a 32 and 64 bit version of our product. I think the best way to handle this is to have separate WyBuild Projects.

That's currently the best way of handling it.

2) We have a few different testing environments to work with: Closed Beta and Public. I thought that this could be handled via having multiple .wyc files, but I have seen no where on how to select the .wyc file within a windows service (running via .NET) in the tutorials or on the forum, so any link or information would be great.

Use -cdata="<filename>" and use the "wyUpdateCommandline" property of the AutomaticUpdater.

3) Lastly, we want to have it so that the public environment is done via a few things, we would allow people to download 'internal versions' (i.e. Greek letters), and release candidates if they so choose, but also have it so that they can just download the stable (or unmarked) versions as well. Is there a way to do that via code (again, utilizing the .NET framework from a service).

Right now, as of wyBuild 2.6.18, the best way to handle that is to use the updatepath variable/commandline switch to dynamically select the "branch" or "channel" of updates the user is allowed to get.

Does that make sense?

All of that makes sense (for the most part). I will start implementing it some time soon, and will update to let you know how everything goes.

Reply
Discard post