Document MTP generated code namespace conflicts in troubleshooting#54008
Open
Evangelink wants to merge 2 commits into
Open
Document MTP generated code namespace conflicts in troubleshooting#54008Evangelink wants to merge 2 commits into
Evangelink wants to merge 2 commits into
Conversation
Adds an FAQ entry under the Microsoft.Testing.Platform.MSBuild troubleshooting section explaining how the generated SelfRegisteredExtensions and MicrosoftTestingPlatformEntryPoint types can collide with referenced types when the project name (and therefore `RootNamespace`) matches a referenced assembly's public type. Shows how to fix the conflict by overriding or clearing `RootNamespace`. Related to microsoft/testfx#7270. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the Microsoft.Testing.Platform (MTP) troubleshooting guidance to document how to fix namespace conflicts caused by MTP MSBuild-generated types when a test project’s RootNamespace collides with types from referenced assemblies.
Changes:
- Add a new troubleshooting FAQ entry describing
RootNamespacecollisions and how to resolve them by overriding or clearingRootNamespace. - Update the article’s
ms.dateto reflect the change date.
Show a summary per file
| File | Description |
|---|---|
| docs/core/testing/microsoft-testing-platform-troubleshooting.md | Adds a new FAQ entry under Microsoft.Testing.Platform.MSBuild describing RootNamespace namespace/type collisions and recommended mitigations. |
Copilot's findings
- Files reviewed: 1/1 changed files
- Comments generated: 2
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
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.
Documents how to resolve namespace conflicts between MTP-generated code (
SelfRegisteredExtensions,MicrosoftTestingPlatformEntryPoint) and types in referenced assemblies whenRootNamespacematches a referenced package's public type (for example, a project namedSystem.Security.Cryptography.ProtectedData.Teststhat also references theSystem.Security.Cryptography.ProtectedDatapackage).Adds a new FAQ entry under Resolve configuration errors > Microsoft.Testing.Platform.MSBuild in the MTP troubleshooting page, showing the recommended fix (override or clear
RootNamespace).Related to microsoft/testfx#7270.
Internal previews