Create and document a staging process for Windows releases #39

andreyvit opened this Issue Apr 4, 2013 · 1 comment


None yet
2 participants

andreyvit commented Apr 4, 2013

  1. Discover a way to override install URL and release a version into a staging environment, so that it can be tested with ClickOnce, but without pushing it into the main autoupdate channel.

    (Hint hint: build with a staging install URL once. Copy that Setup.exe somewhere. Will it install from the staging environment?)

  2. Propose a staging URL on S3 server, have me sign off on it. Preferably, the binary files should be shared, only the app manifest should have a different name.

  3. Create the scripts to release into a staging environment.

  4. Describe the staging process (how to release and how to install a stage version) in a Wiki page of this repo.

@ghost ghost assigned tvasenin Apr 4, 2013


andreyvit commented Apr 4, 2013

Note: it's NOT a requirement for the staging and production versions to co-exist on the same machine. It's OK if the staging version has to be uninstalled before installing the production one.

The intended use is to run the staging version on test VMs, which will not often see the production version installed anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment