Hi everybody,

I'm new here and even my search didn't reveal any answers to me.

I've written a C# SQL application which sort of got successful and we're going to implement it on different levels in a couple of companies. The application uses the native "Publish" method of Visual Studio 2005. My problem is, that when you install application like this, it stores itself deep into user profile on some generated path including the config file.

I am now searching for some reasonable way how to maintain 1 application build but have everyone download the proper config file for it. As the application would query in each organization unit different sql server and also other stuff in the .config file would be different, I still can't find a way how can autoupdate download the proper version without me having to do a separate publish for each unit.

Thanks for any hints and pointers.

I think if you create a custom installer (templates are in VS) you can have a lot more control over all of this, including creating custom prompts. If I understand correctly, you would like a single application build, but allow different config files to be downloaded yes? If thats the case then you could create a custom step in the wizard, prompt the user for their department (or whatever) and then provide custom code to download the appropriate .config file.

Using the installer will also enable you to set a static install path and end the madness! :)

Rob
http://robzyc.spaces.live.com