Rust for the Windows App SDK

(More of a question than an issue. If this repo had Discussions, this would belong there.)

So the xamlapp sample in this repo works nicely.

But if I replace the Button with, for example, a TextBox, it crashes.

Do we (by which I mean "you all") know why?

RatingControl and ColorPicker crash too.

CalendarDatePicker and DatePicker and Slider do not.

I know I'm probably in unsupported/uncharted territory here, but I'm just curious what's going on. Because, in the Swift projection I've been working on, I get exactly the same results: ericsink/SwiftWinRT#3

In fact, running each of these cases under a debugger, the Rust and Swift versions show the same debug messages before failing.

Any insights would be appreciated.

Problem

Running this sample:

fn main() -> ::windows::core::Result<()> {
    println!("starting app");
    bootstrap::initialize()
        .and_then(|_| {
            println!(
                "Remaining charge: {}%",
                PowerManager::RemainingChargePercent()?
            );
            Ok(())
        })
        .and_then(|_| bootstrap::uninitialize())
}

produces this error:

Error: Error { code: 0x80070491, message: There was no match for the specified key in the index. , win32_error: 1169 }

Steps to reproduce

Follow the readme.

Screenshots

Notes

• Output from cargo version:
  cargo 1.57.0 (b2e52d7ca 2021-10-21)

• Output from rustup show: Default host: x86_64-pc-windows-msvc rustup home: C:\Users\lovet.rustup stable-x86_64-pc-windows-msvc (default) rustc 1.57.0 (f1edd0429 2021-11-29)

• Output from rustup --version:
  rustup 1.24.3 (ce5817a94 2021-05-31)

• Output from cmd /c ver: Microsoft Windows [Version 10.0.22000.376]

I'm trying to add a menu bar to the simple window example.

It crashes with exit code 0xc000027b.

To get access to Append() on Children, I added Microsoft::UI::Xaml::Controls::UIElementCollection to windows::build!.

let menu_bar = MenuBar::new()?;
let stack_panel = StackPanel::new()?;
stack_panel.Children()?.Append(&menu_bar)?;
stack_panel.Children()?.Append(&button)?;
window.SetContent(&stack_panel)?;

I know this project is currently experimental, and this isn't a priority, but I figured I'd document in case someone else runs into this.

I'm trying to compile the example in the README from WSL using Linux cross compilation, which includes installing MinGW:

rustup target add x86_64-pc-windows-gnu
rustup toolchain install stable-x86_64-pc-windows-gnu
sudo apt-get install mingw-w64

This seems to almost work (because windows-rs supports cross compilation, it seems) but fails when the linker tries to find the app runtime:

  = note: /usr/bin/x86_64-w64-mingw32-ld: cannot find -lmicrosoft.windowsappruntime.bootstrap
          collect2: error: ld returned 1 exit status
error: could not compile `rust_windows` due to previous error

I'm really not sure how this could be solved, but it would be nice to have the workflow in WSL more clear. Thanks!

Switches out the crate for a new cargo-generate template with the same goals in mind. Also now generates metadata for Microsoft.WindowsAppSDK.Foundation and Microsoft.WindowsAppSDK.WinUI interop types, eliminating the need to manually write and maintain that code.

Problem

The reproducer here performs an access violation, which I don't think ought to be possible in safe rust.

I suspect this is really a bug in windows-rs, related to uninitialization of the field App.Window, but since it involves this crate I'm tentatively putting it here, feel free to move.

Steps to reproduce

1. cargo run

>cargo run
   Compiling simple_window v0.0.0 (C:\Users\drew\CLionProjects\access-violation)
    Finished dev [unoptimized + debuginfo] target(s) in 2.41s
     Running `target\debug\simple_window.exe`
error: process didn't exit successfully: `target\debug\simple_window.exe` (exit code: 0xc0000005, STATUS_ACCESS_VIOLATION)

Screenshots

Notes

• Output from cargo version: cargo 1.53.0 (4369396ce 2021-04-27)
• Output from rustup show:

Default host: x86_64-pc-windows-msvc
rustup home:  C:\Users\drew\.rustup

stable-x86_64-pc-windows-msvc (default)
rustc 1.53.0 (53cb7b09b 2021-06-17)

• Output from rustup --version:

rustup 1.24.3 (ce5817a94 2021-05-31)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `rustc 1.53.0 (53cb7b09b 2021-06-17)`

• Output from cmd /c ver:

Microsoft Windows [Version 10.0.19043.1055]

Hi! I have some questions regarding how the fns are generated, specifically for the XAML part of it.

I've been playing with the metadata generator project and now I'm able to generate the Microsoft.WindowsAppSdk.Generated.winmd file. However, I wonder where do the rest of the winmd files in the .windows/winmd folder come from 🤔. Are those also generated?

I got into generating my own bindings due to the reduced API surface of the windows-rs crate (https://github.com/microsoft/windows-rs/issues/1715) so I just set the min_xaml option to false. That helped and now I can call some more methods like SetContent but I can't seem to find others like Windows::new.

So, in fewer words:

• Are the APIs published in this package under UI::Xaml substantially different from those in windows-rs (even with min_xaml disabled)?
• How/Where can I get the mentioned winmd files?
• Can we have some docs in how to use WinUI 3 from Rust with just windows-rs?
  • I know now we have this amazing crate (windows-app-rs) that simplifies the process, but I think documenting how it works will help people who are trying to experiment with it, use newer preview versions of the WindowsAppSDK or just tweaking it.

Is there a way to add items to the PrimaryCommands collection?

let cmd_bar = CommandBar::new()?;
let add_btn = AppBarButton::new()?;
let add_icon = SymbolIcon::new()?;
add_icon.SetSymbol(Symbol::Add)?;
add_btn.SetLabel("Add Task")?;
add_btn.SetIcon(add_icon)?;
cmd_bar.PrimaryCommands()?.Add(add_btn)?; // something like this

[1] WinUI 3 docs on CommandBar [2] WinUI 3 docs on PrimaryCommands

The beginnings of the windows-app crate. Includes the wiring necessary to bootstrap dynamic dependencies for unpackaged Windows Apps and a native window handle helper.

Problem

I am trying to use the implement macro to implement a subclass of Microsoft::UI::Xaml::Application. It produces a build error

error[E0599]: no function or associated item named `new` found for struct `windows_app::Microsoft::UI::Xaml::IApplication_Vtbl` in the current scope
error[E0599]: no function or associated item named `matches` found for struct `windows_app::Microsoft::UI::Xaml::IApplication_Vtbl` in the current scope

Problem

`target\debug\skeleton.exe` (exit code: 0xc0000409, STATUS_STACK_BUFFER_OVERRUN)
`target\debug\simple_window.exe` (exit code: 0xc0000409, STATUS_STACK_BUFFER_OVERRUN)

Steps to reproduce

Build and launch on Win Server 2019 (with last updates)

Screenshots

Notes

• Output from cargo version: 1.55.0-nightly (cebef2951 2021-07-22)
• Output from rustup show:

Default host: x86_64-pc-windows-msvc
rustup home:  D:\Rust\rustup

installed toolchains
--------------------

stable-x86_64-pc-windows-msvc
nightly-x86_64-pc-windows-msvc (default)

active toolchain
----------------

nightly-x86_64-pc-windows-msvc (default)
rustc 1.56.0-nightly (d9aa28767 2021-07-24)

• Output from rustup --version: rustup 1.24.3 (ce5817a94 2021-05-31)
• Output from cmd /c ver: Microsoft Windows [Version 10.0.17763.2061]