Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle configuration files better for upgrades #110

Closed
ferventcoder opened this issue Feb 21, 2015 · 5 comments
Closed

Handle configuration files better for upgrades #110

ferventcoder opened this issue Feb 21, 2015 · 5 comments

Comments

@ferventcoder
Copy link
Member

No description provided.

@ferventcoder ferventcoder added this to the 0.9.10 milestone Feb 21, 2015
ferventcoder referenced this issue Feb 21, 2015
Backup configuration files as a native way to keep around the
configuration file so that it can be compared to the new one that
overwrite the old (based on the merge strategy from nuget). This is
naive yes, more of GH-10 will later handle this better.
@darrelmiller
Copy link

I'm seeing a renaming issue on upgrades. Not sure what the right solution is though. This happens for all .xml files and all .config files.
image

@ferventcoder
Copy link
Member Author

that's no bueno...

@darrelmiller
Copy link

If the old versions just had a .bak added then I'm assuming that on future upgrades they would not get renamed again.

@ferventcoder
Copy link
Member Author

I think you are correct. I'm a bit leary that this one file was renamed so many times. Do you have relevant log files that you can share in a gist?

ferventcoder added a commit to ferventcoder/choco that referenced this issue May 2, 2015
@ferventcoder
Copy link
Member Author

This is closed with #331

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants