Multiple ClickOnce manifests (slightly OT)

[Marc Gravell]

OK heres an oddity...

I am using a ClickOnce (online only) deployment model; I have various
servers (primarily for different environments: testing, production etc), and
I want to have a *similar* manifest on each, with the main difference being
the config file (so that each connects to appropriate servers). To get
around the hashing on the config file, I simply publish the app (via
MSBuild) several times with different app.config contents each time.

The problem:
* (assume empty app-cache)
* Hit .application on download-server "A" - this downloads the app and
starts talking to web-service server "a" (correctly based on web.config)
* Close app
* Hit .application on download-server "B" - this then *also* starts talking
to web-service server "a", even though the config file on "B" says "b"

Obviously the runtime is deciding that they are the same app, and re-using
the cached copy.

So - can I fix it?

Is there any way (preferably automated either via some bespoke C# or just
MSBuild command-line parameters) of telling it that the two should be
treated separately? Preferably while using the same code-signing
certificate?

Thanks in advance,

Marc