Home All Groups Group Topic Archive Search About

Click once and exe.config file

Author
25 Aug 2006 9:55 AM
Greg
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.

Author
25 Aug 2006 12:52 PM
Cowboy (Gregory A. Beamer)
No matter how you install, you can set up custom installers that can edit
files, like the config file. Set up the custom installer as a wizard and ask
the user to identify his server. You can also bootstrap the SQL Express
product, if they do not already have a database.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

*************************************************
Think outside of the box!
*************************************************
Show quote
"Greg" <gregwilliams***@yahoo.co.uk> wrote in message
news:1156499748.544170.234250@h48g2000cwc.googlegroups.com...
> 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.
>
Author
25 Aug 2006 1:11 PM
Greg
Thanks for the advice.

The user will actually need to be able to edit the config file
occasionally once the product is installed, so enabling the installer
to edit the files isn't going to help me here unless the user
re-installs their product to acquire the new settings.

Regards,

Greg.

Cowboy (Gregory A. Beamer) wrote:
Show quote
> No matter how you install, you can set up custom installers that can edit
> files, like the config file. Set up the custom installer as a wizard and ask
> the user to identify his server. You can also bootstrap the SQL Express
> product, if they do not already have a database.
>
> --
> Gregory A. Beamer
> MVP; MCP: +I, SE, SD, DBA
>
> *************************************************
> Think outside of the box!
> *************************************************
> "Greg" <gregwilliams***@yahoo.co.uk> wrote in message
> news:1156499748.544170.234250@h48g2000cwc.googlegroups.com...
> > 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.
> >

AddThis Social Bookmark Button