Bug: Why CppWinRTModuleInclude not auto include the dependencies of include modules

Version

3.0.260520.1

Summary

When we use CppWinRTModuleInclude, we expect that we can write the module which we need so that we do not need to generate everything. But when we add it, we will find that it is useless because it indeed only generates the module we write but not consider the dependencies which the module referenced. So that we need to write all dependencies manually. But the dependencies of dependencies of dependencies will be almost all namespace to include. We are almost unable to find out all the dependencies.

Reproducible example

Add

<CppWinRTModuleInclude>
  Windows.Foundation
</CppWinRTModuleInclude>

Then try to fix the dependencies. Do not say use CppWinRTModuleExclude, we need use all the member under Windows.Foundation and do not want to know what they dependence.

Expected behavior

C++/WinRT should add all used module.

Actual behavior

C++/WinRT only add Windows.Foundation.

Additional comments

I don't think it is a feature. Or the C++/WinRT should include all Windows.* modules just like C#/WinRT so that when we add third part CppWinRTModuleInclude it can correctly reference the Windows.* modules.

Beginne damit, die Implementierung der Option CppWinRTModuleInclude und den Pfad zur Generierung von Modulabhängigkeiten zu finden. Reproduziere das Problem mit Windows.Foundation und untersuche, wie referenzierte Module aufgelöst werden. Als erledigt gilt die Aufgabe, wenn die generierte Ausgabe alle von Windows.Foundation und seinen Abhängigkeiten verwendeten Module enthält, ohne dass jeder Namespace manuell aufgeführt werden muss.