Skip to content
This repository has been archived by the owner on Nov 20, 2018. It is now read-only.

Rename UserSecrets tool to UserConfig #277

Closed
danroth27 opened this issue Mar 18, 2017 · 5 comments
Closed

Rename UserSecrets tool to UserConfig #277

danroth27 opened this issue Mar 18, 2017 · 5 comments

Comments

@danroth27
Copy link
Member

The User Secrets tool is useful for more than just secrets. It's nice for any configuration data that is user specific and shouldn't be shared via source control. Consider renaming it accordingly.

@natemcmaster
Copy link
Contributor

natemcmaster commented Mar 20, 2017

I'm generally against renaming RTMed packages. NuGet doesn't support renames or redirects, which means renaming a package ID breaks upgrade scenarios.

cref NuGet/Home#1590

@natemcmaster
Copy link
Contributor

@muratg @glennc what are your thoughts on this? If we're gonna do rename the package, we should do it ASAP.

@muratg
Copy link

muratg commented May 1, 2017

It's a product (and hence a "PM") question :trollface:. Though if we want to go with this, I guess we can create a 2.0 version of the package with the old name as well and tell people to change their dependencies to the new name.

@muratg muratg added this to the Backlog milestone Sep 28, 2017
@muratg
Copy link

muratg commented Sep 28, 2017

@danroth27 @DamianEdwards I don't think you'll want to rename this in 2.1 so backlogging.

@natemcmaster
Copy link
Contributor

I think at this point its too late for a rename, especially now that it's bake into the SDK.

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

No branches or pull requests

3 participants