Merged
Conversation
…nt with UserSecrets.
|
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Most or all of preview2 updates, pending a conversation about user secrets in VS.
Legal stuff.
And remove old sample from .sln file.
Actually include new sample this time.
Update sample to Web Application rather than website.
Rev to preview2.
Update Json.Net.
Update Azure to use connection string.
Don't default to App_Data for UserSecrets.
Update UserSecrets doc description.
Use 'optional' instead of 'ignoreMissingFile' for Json to be consistent with UserSecrets.
Update UserSecrets to better handle UserSecretsId from VS.
Repo Cleanup
Fix Json builder when file is not found.
Add Signing
Initial Cleanup