Code gen

[pranavkm]

Follow up from the discussion in #40342

[dougbu]

This looks fine to me (as long as it works 😺).

Curious: How did you decide between the separate TrimmableProject.props option and adding %(TrimmableProject) metadata in ProjectReferences.props❔

[JamesNK]

Love it.

Out of curiosity, do you have an aspiration to eliminate the component's WASM linking test project? Setting the WASM build properties is simple enough. The more difficult part is distinguishing between trimmable WASM projects and trimmable aspnetcore projects.

[pranavkm]

Curious: How did you decide between the separate TrimmableProject.props option and adding %(TrimmableProject) metadata in ProjectReferences.props❔

I followed the pattern for SharedFxDepList - assumed separate files were the way to go. Should I merge the contents?

Out of curiosity, do you have an aspiration to eliminate the component's WASM linking test project?

Right now, this test tests trimmability for all projects in the repo include the WebAssembly ones. I didn't do anything to exclude it since it appears to just work. If we can get some confirmation in the coming ways it doesn't get in the way of doing things, we can remove the WASM specific one.

[dougbu]

Should I merge the contents?

Nope. Just wondered about reasonzzz; I have no objections to a separate file, especially because the added information is used in only a couple of places.

I'm doing something similar for #40242 and require a separate file because the info I'm adding isn't specific to project reference providers. That didn't apply here.

[JamesNK]

@pranavkm This got closed when I merged my PR. Rebase and open a new PR and I'll approve 🙏