Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs for adding Windows App SDK to an existing project does not instruct devs to depend on the framework package. #2673

Closed
dhoehna opened this issue Jun 24, 2022 · 1 comment
Assignees
Labels
area-DeveloperTools Issues related to authoring (source and IDL), debugging, HotReload, LiveVisualTree, VS integration bug Something isn't working

Comments

@dhoehna
Copy link
Contributor

dhoehna commented Jun 24, 2022

Describe the bug

Adding Windows App SDK to an existing project does not mention that, for MSIX apps, a PackageDepndency node needs to be added to the manifest.

Is the dependency is not declared, the thrown error is "Class not registered" Not very helpful.

Additionally, the steps to add the dependency isn't straight forward.

  1. Install the framework package, if not installed already.
  2. run get-appxpackage to find the framework package.
  3. Add a package dependency node to the package manifest.
  4. Copy the Name, publisher, and min version over from Powershell to the manifest.

A new windows developer might not be able to tie these steps together.

Steps to reproduce the bug

  1. Make a desktop bridge project
  2. Use a Windows App SDK component.
  3. Use the desktop bridge project to make an MSIX package.
  4. Run the package.

The app will crash.

Expected behavior

Docs should point out this extra step.

Screenshots

No response

NuGet package version

No response

Packaging type

No response

Windows version

No response

IDE

Visual Studio 2022

Additional context

No response

@ghost ghost added the needs-triage label Jun 24, 2022
@btueffers btueffers added area-DeveloperTools Issues related to authoring (source and IDL), debugging, HotReload, LiveVisualTree, VS integration bug Something isn't working and removed needs-triage labels Jun 27, 2022
@dhoehna
Copy link
Contributor Author

dhoehna commented Sep 25, 2023

Closing. I tried to re-create the issue with a windows packaging project and ran into no issues.

@dhoehna dhoehna closed this as completed Sep 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-DeveloperTools Issues related to authoring (source and IDL), debugging, HotReload, LiveVisualTree, VS integration bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants