Results 1 to 6 of 6

Thread: How to change the file path of the app config/settings file?

  1. #1

    Thread Starter
    Hyperactive Member
    Join Date
    Sep 2007
    Posts
    360

    How to change the file path of the app config/settings file?

    How can I change the file path of the app config/settings file? The settings file gets wiped out when I deploy an update with clickonce. I'd like to store the file within a folder in My Documents.

  2. #2

    Thread Starter
    Hyperactive Member
    Join Date
    Sep 2007
    Posts
    360

    Re: How to change the file path of the app config/settings file?

    Anyone anyone anyone.

  3. #3
    Super Moderator jmcilhinney's Avatar
    Join Date
    May 2005
    Location
    Sydney, Australia
    Posts
    110,299

    Re: How to change the file path of the app config/settings file?

    You cannot decide where the config file resides. I don't think it should be an issue anyway though, as it's my understanding that ClickOnce merges existing settings into the new version.

    http://msdn.microsoft.com/en-us/library/ms228995.aspx

    I've never actually deployed using ClickOnce so I'm going to test this out for myself tomorrow.

  4. #4

    Thread Starter
    Hyperactive Member
    Join Date
    Sep 2007
    Posts
    360

    Re: How to change the file path of the app config/settings file?

    All settings are lost after the user updates.

  5. #5
    Your Ad Here! Edneeis's Avatar
    Join Date
    Feb 2000
    Location
    Moreno Valley, CA (SoCal)
    Posts
    7,339

    Re: How to change the file path of the app config/settings file?

    You can persist settings for ClickOnce. There is a better article on MSDN somewhere but this should work also.
    http://www.devx.com/dotnet/Article/33944/1954

  6. #6
    Super Moderator jmcilhinney's Avatar
    Join Date
    May 2005
    Location
    Sydney, Australia
    Posts
    110,299

    Re: How to change the file path of the app config/settings file?

    Quote Originally Posted by Edneeis
    There is a better article on MSDN somewhere
    I know I've seen such an article before but my quick initial serahc didn't turn it up. I was going to have a more thorough look today. It seems I don't have to because this:
    Quote Originally Posted by Edneeis
    addresses the current issue in the second last section, very near the bottom of the page.

    I really should have a proper play around with ClickOnce some time though. So many things to have a play around with; so little time.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width