Hi All,

I wonder if someone could help me;

I have a scenario where i need to target multiple clients using the same win forms application.
This application uses a client/server architecture and each clients iteration of the software will be on a different server.
Basically each client will not know about the other and they will each have their own installation of the software using clickonce. This means their own entry in the start menu and potentially each client could be working of different code bases (think branching in subversion).

The problemI’m facing is when i try and release to different servers and then install on a machine that already has the software on it (for testing and support purposes). For example i currently have a development server and a testing server. When i try and build an instance of the software for each server this is fine. I change the Publish Options, the installation folder URL and the publish folder location.

This all works fine, however when i try and install to a machine that already has the application, the new version tries to replace the old one and when it tries to launch it says the application cannot be launched.

The only way i can get around this is by changing the Assembly Name of the application. However this causes internal errors to the application that are not being picked up by the compiler because i use reflection that relies on the assembly name. I could use a config key to load in different assembly names for different clients but this very nasty.

I’ve also tried changing the GUID for each client but this has no affect.

Does anyone have any other ideas? or this not possible?

Regards

Dave

Thank you for the response.

I figured as much and have modified the reflection code to support different Assembly Names.