Clarifies Source Generator Ambiguities and Disabling#411
Merged
Conversation
Adds documentation explaining ambiguous reference issues caused by internal partial source-generated classes, details how to disable specific generators via MSBuild properties, and updates README navigation to source generator docs.
This was referenced Mar 16, 2026
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
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.
Adds comprehensive documentation to clarify potential ambiguous method call errors that can occur when
Moq.AutoMocksource generators are enabled across multiple test projects with shared visibility.Provides detailed instructions on:
internal partialclasses)..csprojfile.This update aims to improve user experience by addressing a common pain point and providing clear guidance for configuration.
Relates to #410