CommunityToolkit / CommunityToolkit/Windows

AttachedCardShadow crashes side-loaded packaged WinUI 3 app

Open
#207 25 comments 1 reaction 1 assignee Assigned to @Arlodotexe View on GitHub
bug components::media help wanted
Dominant language
C#
Stars
1.1k
Forks
166
PR merge metrics
No merged PRs in 30d

Description

## Describe the bug

When using AttachedCardShadow anywhere in my app (WinUI3 / WinAppSDK 1.0), it runs fine from Visual Studio.
But as soon as I package the app and run it, the app crashes.
I get the following stack trace:
![image](https://user-images.githubusercontent.com/4835617/144197856-0b6ffca9-da1e-4beb-94b0-116d50c92611.png)

The exception message is:
"System.Runtime.InteropServices.COMException: Class not registered (0x80040154 (REGDB_E_CLASSNOTREG))"

## Steps to Reproduce

Unfortunately I can't reproduce this in a sample app that starts with the newest templates.
My app was converted from one of the earliest ProjectReunion version to all subsequent versions until the current Windows App SDK 1.0 release.
I can't find major/important differences in the project files (csproj and wapproj), though.
Steps to reproduce the behavior:

1. Use AttachedCardShadow anywhere in the app.
2. Sign manifest
2. Package using: Publish | Create App Packages...
3. Install by running the Add-AppDevPackage.ps1
4. Run
## Expected behavior

The app should run without a crash

## Screenshots

## Environment

![image](https://user-images.githubusercontent.com/4835617/144197985-a127030e-6f4c-46ee-ae3f-66dea4dcc053.png)
![image](https://user-images.githubusercontent.com/4835617/144198038-3947738e-8098-413f-a3ac-3720db7351de.png)

NuGet Package(s):

Package Version(s):

Windows 10 Build Number:
21H2 / 19044.1348

App min and target version:
Min: April 2018 Update (17134)
Target: May 2020 Update (19041)

Device form factor: Desktop

Visual Studio version:
2022 (17.0.1)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.