Fix Deterministic compiler option default value documentation #47725
+5
−1
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 documentation for the
Deterministic
C# compiler option was misleading about the default behavior. The previous text stated "By default, compiler output from a given set of inputs is unique, since the compiler adds a timestamp and an MVID..." which implied that deterministic compilation was disabled by default.However, for modern .NET projects (including MAUI projects as mentioned in the issue), the .NET SDK actually sets
Deterministic=true
by default. This was causing confusion for developers who expected the default to befalse
based on the documentation.Changes Made
Deterministic
property defaults totrue
)Validation
Tested with actual .NET projects to confirm:
Deterministic = true
(confirmed in build output)<Deterministic>false</Deterministic>
works as expectedtrue
This ensures the documentation accurately reflects the actual SDK behavior that developers experience.
Fixes #33380.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.
Internal previews