469,612 Members | 2,658 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,612 developers. It's quick & easy.

ClickOnce

I have a WinForm(VB 2.0) application that I am publishing as a ClickOnce
installation. We have a need to publish the same application code for several
configurations. (Staging, TestSystem, LiveSystem) Each of these
configurations differ only in app.Config changes. I would like the ability to
install all of these side-by-side on a machine. Also, we QA our Staging build
before publishing as live, and I am concerned that I have the ability to
assure both builds are identical even though they are published days apart.
Any suggestions?

Jun 30 '06 #1
3 1551
On the project Properties page/Application Tab click the "Assembly
Information" button and set the Assembly Version and File Version Numbers

Then in Publish Tab set your publish version.

Everytime you publish, you will get a new publish folder on the server when
you change these numbers

Rich

"KenL" wrote:
I have a WinForm(VB 2.0) application that I am publishing as a ClickOnce
installation. We have a need to publish the same application code for several
configurations. (Staging, TestSystem, LiveSystem) Each of these
configurations differ only in app.Config changes. I would like the ability to
install all of these side-by-side on a machine. Also, we QA our Staging build
before publishing as live, and I am concerned that I have the ability to
assure both builds are identical even though they are published days apart.
Any suggestions?

Jun 30 '06 #2
Hi!

A follow up question when "The application is available offline as well".

We also have these environments, Staging, TestSystem, LiveSystem and so on
with different ClickOnce Publishing Locations (servers).

Let us say that I "Publish" the Staging-version. Is then first set "Publish
Options | Product name" to something like "...Staging..." so that the user
that installes the application understand agains which web service the
application is communicating with. Ok, everything is fine.

The problems starts when trying to "Publish" e g the "TestSystem" version. I
then simply change the Product name to "..Test..." (and of course change
publishing location). But what happens when the client installs from this new
installation URL, is that the previous installation is REMOVED.

That is not what I want. I want the different installations to live side by
side on the clients, with different Start menu shortcuts "Staging",
"TestSystem", "LiveSystem".

What more must be different, besides "Product name", to make the ClickOnce
logic to understand that they should be handled as parallell
applications/installations.

Best regards,
Benjamin,
Sweden
Jul 12 '06 #3
Hi!

I used a MSDN support case to bring light on this issue.

You have to change the project property Assembly Name to make the
ClickOnce-applikation unique.

Of course you also change "Publish options | Product name" to let the user
see the different for another ClickOnce application, but theoretical that is
no requirement.

Best regards
Benjamin,
Sweden

Sep 27 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

5 posts views Thread by Danny Tuppeny | last post: by
3 posts views Thread by Asaf | last post: by
1 post views Thread by moondaddy | last post: by
8 posts views Thread by Tina | last post: by
1 post views Thread by M O J O | last post: by
2 posts views Thread by Alex Bögli | last post: by
1 post views Thread by Earl | last post: by
3 posts views Thread by =?Utf-8?B?Um9nZXIgVHJhbmNoZXo=?= | last post: by
reply views Thread by devrayhaan | last post: by
reply views Thread by gheharukoh7 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.