Remove ignore on *.DotSettings.user since it's covered in *.user and keep publi… #3812
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…sh settings since private info is in the pubxml.user
|
Is this a problem just for you? Can you point to any public discussions on this issue? |
|
No, this is a problem for anyone I've talked with, they general don't use the VS .gitignore for this issue and just re-use their own. I did not look at any public discussion but if you create a new repo with this gitignore, then create a publish profile to push to azure or w/e server you want, check your code in, then try and reference that publish profile on your build server it will fail (because publish profiles being checked in is ignored by default). I don't see how that's a good thing? |
|
I guess the main reason this was ignored was because connection strings to databases fully get stored in the pubxml? Is that the reason? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…sh settings since private info is in the pubxml.user
Reasons for making this change:
Everytime i add a publish profile to a new solution i always get tripped up because pubxml is ignored... this is a huge pain since i want the server name etc in there. Passwords are already stored hidden in the pubxml.user which is ignored.