-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Non deterministic ordering of preSolution, postSolution and folder items #251
Comments
Yes I'd like to keep the generation deterministic and in line with what Visual Studio would do. Does VS re-order anything when you open it? I recently moved to the NuGet team and am a little swamped at the moment, any contributions are welcome! |
Congrats Jeff 🎉🎉🎉 |
VS doesn't update the solution file unless you explicitly save it. Using System.CodeDom.sln as an example, here's the diff that VS produces when explicitly saving the solution file: https://www.diffchecker.com/oNirSFSA. |
Project ordering is replicated in the ProjectConfigurationPlatforms section by Visual Studio. But SlnGen uses a diffrent ordering for them. This change uses the same ordering for both sections. Fixes microsoft#251
Project ordering is replicated in the ProjectConfigurationPlatforms section by Visual Studio. But SlnGen uses a diffrent ordering for them. This change uses the same ordering for both sections. Fixes #251
Using the latest version of slngen results in this diff when using to update the Microsoft.Extensions.Options.DataAnnotations solution file:
Would it be possible to not reorder elements that haven't changed? From looking into multiple diffs I notice this often happening with the following elements:
cc @jeffkl
The text was updated successfully, but these errors were encountered: