microsoft / microsoft/WindowsAppSDK
App broken by DeploymentManagerAutoInitializer.cs throw COMException
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 4.7k
- Forks
- 471
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 28
Description
### Describe the bug
App broken by running `var options = new global::Microsoft.Windows.ApplicationModel.WindowsAppRuntime.DeploymentInitializeOptions();` in `DeploymentManagerAutoInitializer.cs`. It works fine when I jump out of it.
### Steps to reproduce the bug
1. Create a Windows App SDK project
2. Run it
### Expected behavior
Running succeed.
### Screenshots
### NuGet package version
Windows App SDK 1.8.0: 1.8.250907003
### Packaging type
Packaged (MSIX), Unpackaged
### Windows version
Windows 11 version 24H2 LTSC (26100, June Update)
### IDE
Visual Studio 2022-preview
### Additional context
_No response_
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure in a Windows App SDK 1.8 project using both Packaged (MSIX) and Unpackaged configurations on the reported Windows 11 version. Inspect DeploymentManagerAutoInitializer.cs and the DeploymentInitializeOptions construction, then verify that running the app no longer throws the reported COMException.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100