I'm about to release a application to a customer. This app uses a
config file to store connection settings. I'd like to be able to create
a "Click Once" installer, as this will remove lots of dependency issues
that are likely to arise with this app. However, my understanding of
click once is that the application is installed to a obscure location,
thus making it difficult for the customer to locate the config file in
order to edit the settings.

Is there an easy way around this, or given the requirements, would I be
best advised to create a traditional installer package?

I'd be grateful for any comments, as its vital I get this working
correctly!

Greg.

You can use the new Settings properties of your project. Then provide
an interface by which your users can modify the settings. Alternately,
y ou can store settings in the registry, which may be a better option
(i'm not sure if Settings get carried forward on upgrades).

Greg wrote:
> I'm about to release a application to a customer. This app uses a
> config file to store connection settings. I'd like to be able to create
> a "Click Once" installer, as this will remove lots of dependency issues
> that are likely to arise with this app. However, my understanding of
> click once is that the application is installed to a obscure location,
> thus making it difficult for the customer to locate the config file in
> order to edit the settings.
>
> Is there an easy way around this, or given the requirements, would I be
> best advised to create a traditional installer package?
>
> I'd be grateful for any comments, as its vital I get this working
> correctly!
>
> Greg.