Reorder properties on Application page #7038
Merged
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
drewnoakes
added
the
Feature-Project-Properties-Designer
tmeschter
approved these changes
Mar 23, 2021
Yes I also contemplated this. Once we get telemetry around the frequency of property updates, we can revisit ordering using actual data to inform these decisions. |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
Historically in legacy projects, the Assembly Name and Default Namespace properties were manually kept in sync with the project by the user. With SDK-style projects, it's more common to go with the default behaviour of picking up the MSBuildProjectName property, which is computed from the project's file name. Given these properties are far less likely to be user edited, we move them further down the UI, allowing more commonly modified properties to rise to the top.
drewnoakes
force-pushed
the
reorder-application-page-properties
branch
from
27e4a5e to
4112be3
Compare
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.
Historically in legacy projects, the Assembly Name and Default Namespace properties were manually kept in sync with the project by the user.
With SDK-style projects, it's more common to go with the default behaviour of picking up the
MSBuildProjectNameproperty, which is computed from the project's file name.Given these properties are far less likely to be user edited, we move them further down the UI, allowing more commonly modified properties to rise to the top.
Microsoft Reviewers: Open in CodeFlow