Clarify relationship between project and directory names #9830
Conversation
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
The project name does not have to match the directory name, although they are usually created in this way. I feel this change makes it clearer where the default `<AssemblyName>` and `<PackageId>` properties come from.
BillWagner
approved these changes
Feb 22, 2019
There was a problem hiding this comment.
Thanks for making this change @drewnoakes We appreciate it.
I've reviewed the change, and I'll 
now.
Thanks for contributing again to docs!
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.
The project name does not have to match the directory name, although they are usually created in this way. I feel this change makes it clearer where the default
<AssemblyName>and<PackageId>properties come from.A subject matter expert should confirm this however.