One approach is to use [application settings][1], which we used for a WPF application deployed with ClickOnce.  We have multiple settings for such things as user specified download folders, default settings, etc.  For each such setting, the *Scope* is set to User.  When the setting is changed by the user the new values are persisted with a call such as:

    YourProject.Properties.Settings.Default.UserSetting1 = "New Value";
    YourProject.Properties.Settings.Default.Save(); // persists the new value for the current user

Even with multiple updates of the application via ClickOnce, these settings are persisted for each user.  Note that the settings are persisted on a per-machine basis, so if a user goes to a new machine and downloads the application, their settings will not be transferred.

Hope this helps,


  [1]: http://msdn.microsoft.com/en-us/library/k4s6c3a0%28v=vs.100%29.aspx

I'd like to deploy a ClickOnce application, but would like to have a configurable user file to store settings and preferences that does not get overwritten everytime I publish a new version.  Is there to specify that a particular file should get deployed in any installation that doesn't already have one, but not overwrite any previous versions?

The only workaround that I can envision is to store the data in a database, but it's so user-centric that it seems like a lot of overhead to re-invent the config file.

ClickOnce Deployment with local user file

### [Configuring a publishing source for GitHub Pages][1] (very limited)

While you *can* select a folder as the source for gh-pages, you can *only* do so for the `/docs` directory at the parent level, and you *still* have to actually commit the built files in order to do so, which means you'll have to override the `.gitignore` and commit them twice

<img src="https://i.stack.imgur.com/ggDJH.png" width="313"/>

### Automated Deploy Scripts

If you're using npm, there are a couple packages that handle publishing sub-directories to gh-pages.  Install with option `--save-dev` to add it to your `devDependencies`:

* [**push-dir**][2]

    
    
        # install
        $ npm install push-dir --save-dev
        
        # usage
        $ push-dir --dir=dist --branch=gh-pages

* [**gh-pages**][3]

    
    
        # install
        $ npm install gh-pages --save-dev
        
        # usage
        $ gh-pages -d dist

In either case, if get a command line tool working for you and get it configured with the right options, you can alias it in your `package.json` like this:



    "scripts": {
      "deploy": "npm run build && gh-pages -d dist"
    }

**Further Reading**: 

* [Deploying a subfolder to GitHub Pages][4]
* [Deploy Vue to GitHub pages-the easy way!][5]

[1]: https://help.github.com/articles/configuring-a-publishing-source-for-github-pages/
[2]: https://www.npmjs.com/package/push-dir
[3]: https://www.npmjs.com/package/gh-pages
[4]: https://gist.github.com/cobyism/4730490
[5]: https://medium.com/@codetheorist/vue-up-your-github-pages-the-right-way-955486220418

I was trying to publish my -username-.github.io repository to github pages but my `index.html` is inside `dist` folder.

I cannot use `git subtree push --prefix dist origin gh-pages` because this is meant for project pages, not user/org pages.

All I want is, github to treat dist as root directory for hosting user/org page.  Please help.Thanks

PS: I don't want to do redirection hack.
