Append additional metadata in targets file, to preserve project settings

[Scottj1s]

fixes #593

[kennykerr]

/azp run

[azure-pipelines]

No pipelines are associated with this pull request.

[riverar]

In the case of a simple console app that simply:

• Adds the NuGet package
• Has a single winrt::init_apartment(); call

Projection headers get generated. As far as I know, in the above case, none of these are true (from README):

• NuGet package references containing winmd files
• Other project references producing winmd files
• Raw winmd file references

Which means this part of the README isn't true (emphasis mine):

[...] For any winmd file discovered above, C++/WinRT creates reference (consuming) projection headers.

Am I missing something?

[Scottj1s]

In the case of a simple console app that simply:

• Adds the NuGet package
• Has a single winrt::init_apartment(); call

Projection headers get generated. As far as I know, in the above case, none of these are true (from README):

• NuGet package references containing winmd files
• Other project references producing winmd files
• Raw winmd file references

Which means this part of the README isn't true (emphasis mine):

[...] For any winmd file discovered above, C++/WinRT creates reference (consuming) projection headers.

Am I missing something?

The first bullet is true:

• Platform winmd files in the SDK (both MSI and NuGet)

These are not "referenced" directly by the project (so I'm avoiding that term), but are still "discovered" and processed by cppwinrt.exe to produced headers.

[riverar]

Oh got it! The existence of the platform winmd files is the trigger.