This project brings the capability for interop between Windows Runtime and Rust, where most of the tasks are done through Rust-native features and Cargo. However in some cases, Visual Studio, or MSBuild precisely, must be used. Consider some scenarios:

• XAML compilation. I did a quick search, and it turned out the internal processor is tightly coupled with languages. It seems non-trivial to workaround in a Rust Cargo project. The only thing I can do is to create a new C# or C++/WinRT UWP application with Visual Studio and extract generated *.xbf files.
• Application packaging and signing. These tasks could be achieved by executing command line tools, but in a complicated and error-prone way.
• Inside a Solution. Since MSBuild is unaware of Rust Cargo projects, it could be confusing when someone Cleans and Rebuild the whole Solution but Rust projects remains unchanged.

Actually I am not sure whether this issue is directly related here or Visual Studio, or both. Are there any plans or roadmaps regarding this issue on winrt-rs side?