I probably didn’t explain, my idea is not a static page but an asp page (or
something more modern) that reads the version and decides what to return.
The contrived example is actually based on a real scenario, the sales/marketing
people still called the application v1 but we had to drop Windows XP support in
a point release so not all versions could be upgraded. I could have changed
version under the covers but it was easier not to.
In my scenario I have to allow less-techy people to handle the release and
upgrade process and they seem happy to edit an asp page (this is based on a
home grown upgrade process before bundles).
I am still not totally sure what you are suggesting, what would you put on the
server?
Neil
From: Rob Mensching [mailto:[email protected]]
Sent: 20 February 2013 20:45
To: Windows Installer XML toolset developer mailing list
Subject: Re: [WiX-devs] WixStdBA and bundle self updates
Upgrade logic is still on the server. The server decides what to serve back at
the url.
With this scheme it is harder to do your scenario if you have a static file.
Although, the straight forward fix with static URLs is to release a 1.9.1 that
fixes the update url in the Bundle. Plus, that scenario *does* feel a bit
contrived. <smile/>
I'm just wondering if its easier to just push up a new bundle than to have to
push up a new bundle and update another file? Have to document another file
format, although maybe we could just put the URL in a text file... but if we
did that, that's the same as having the server just do a 302 itself. Which is
why I end up back at just pointing to the bundle. <smile/>
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
