Other Source Generators in Uno projects

[HavenDV]

I noticed that the Uno package started blocking the use of third-party generators. In my case, I was generating View code behind constructor code in my test project.
Is this a bug or is it a special behavior to limit the possible problems of using other generators in most cases? In second case, just need to create a library that will call these generators and use it already in Uno

I assume it is caused by this code

uno/src/SourceGenerators/Uno.UI.SourceGenerators/Content/Uno.UI.SourceGenerators.props

Lines 362 to 363 in 2ed9559

	<_AdditionalFilesCleanup Include="@(AdditionalFiles)" />
	<AdditionalFiles Remove="@(_AdditionalFilesCleanup)" />

P.S. I did not find any changes in the code that would explicitly prohibit the use of other generators. But I still can't achieve using another generator in a project with Uno.UI.WebAssembly. This may be related to dotnet updates to 6.0.2 or VS to 17.2 preview

Repro:
ratbuddyssey-master.zip

1. Build Ratbuddyssey.Apps.Uno.WebAssembly. The generator will not show the generated file (it should appear if at least one AdditionalFile exists at the time of generation)

2. This is not a bug related to the generation order. If you remove Visible="False" then you can see that AdditionalFile exists before the start of build. But it seems then some MSBuild code removes AdditionalFile at one of the stages of preparation. 3. ViewBase code is generated in another library (Ratbuddyssey.Apps.Uno.Core.Standard) and available for Uno generator

[jeromelaban]

This particular behavior is not intentional, and it's not preventing other generators to run but rather removing unrelated additional files.

Let's open #8176 to track this.