B
Bill
I have a WinForms application with a config file that I would like to deploy
internally by making it available on a central server, where it will be
maintained and versioned. I was thinking that accessing it via IE would be
helful, but it is not clear how to handle the config file, which does thinks
such as activate the client remoting capabibility. I would like changes to
this config file to be automatically downloaded with the application.
There is also the problem of default permissions. Although this can be
handled with isolated storage, it is not clear how I can automatically
download any changes to the config file in the central server to this
location.
Is this approach an acceptable one or is there a better method for
accomplishing what I am attempting to accomplish.
internally by making it available on a central server, where it will be
maintained and versioned. I was thinking that accessing it via IE would be
helful, but it is not clear how to handle the config file, which does thinks
such as activate the client remoting capabibility. I would like changes to
this config file to be automatically downloaded with the application.
There is also the problem of default permissions. Although this can be
handled with isolated storage, it is not clear how I can automatically
download any changes to the config file in the central server to this
location.
Is this approach an acceptable one or is there a better method for
accomplishing what I am attempting to accomplish.