`GenerateSelfRegisteredExtensions` is undocumented in dotnet/docs

[Youssef1313]

@Evangelink Is it missing? Or intentionally undocumented?

[Evangelink]

It's missing, it's been added recently and I have failed to keep up with ensuring all the changes were properly documented.

[SimonCropp]

can you point to the docs page where this should be added, in case someone wants to pick it up

[Youssef1313]

@SimonCropp It should be around this, along with GenerateTestingPlatformEntryPoint

[Youssef1313]

I think most end-users don't care about this property and they don't need to use this property. So closing out as not important to document.

[sharpjs]

This property appears to be needed when all are true:

• Test assembly Foo.Bar references test assembly Foo.
• Test assembly Foo has <InternalsVisibleTo Include="Foo.Bar" />

Without setting GenerateSelfRegisteredExtensions to false, the following confusing error occurs:

(path)\obj\Debug\MicrosoftTestingPlatformEntryPoint.cs(15,13,15,37): warning CS0436: The type 'SelfRegisteredExtensions' in '(path)\obj\Debug\SelfRegisteredExtensions.cs' conflicts with the imported type 'SelfRegisteredExtensions' in '(other-project), Version=...'. Using the type defined in '(path)\obj\Debug\SelfRegisteredExtensions.cs'.

Such a situation is more likely to occur in larger projects that split test suites into multiple parts. That's how I encountered it. Right now, this GitHub issue is what search engines find.

IMO, this property is worthy of documentation.

[Youssef1313]

@sharpjs The above scenario should normally work fine without needing GenerateSelfRegisteredExtensions. The fact that it doesn't work is actually a bug (lack of using globalized fully qualified names in generated code).

This property alone isn't the right fix for that scenario, is that means all extensions installed in the project will be skipped (unless you re-write the entrypoint yourself)

[Youssef1313]

The team should also consider marked SelfRegisteredExtensions with EmbeddedAttribute.

[Youssef1313]

Tracked in #8879

[sharpjs]

This property alone isn't the right fix for that scenario, is that means all extensions installed in the project will be skipped (unless you re-write the entrypoint yourself)

I'm new to MTP and did not realize I would need to write a custom entry point for my case (until an update is released containing your fix). I do now. Thank you for the advice, @Youssef1313! You saved me several hours of confusion.