Closed ToolmakerSteve closed 1 week ago
I was not following the correct documentation.
The doc I needed to follow is:
Create your first WinUI 3 (Windows App SDK) project / Unpackaged.
I was missing this step:
Add the following property to your project file ...
<WindowsPackageType>None</WindowsPackageType>
Describe the bug
The template "Blank App, Packaged (WinUI 3 in Desktop)" should include needed references so that "Debug | AppName (Unpackaged)" can be run and debugged.
Failing that, Getting Started documentation should describe what references are needed, and how to add them explicitly to the project.
Failing that, I need to know how to discover what references are missing, so I can add them manually to
bin
folder.Why I care:
Porting a large legacy .Net Framework project to Windows App SDK.
For developer productivity, it is essential that the project be debuggable without performing packaging.
Making and testing changes has always been very quick; any step that slows this down is a significant development cost.
I have no idea how to find and fix whatever is missing.
Steps to reproduce the bug
New Project from template "Blank App, Packaged (WinUI 3 in Desktop)".
Deploy Debug | x64 | AppName (Package) => success: "WinUI Desktop" window with button "Click Me" that works.
Deploy Debug | x64 | AppName (Unpackaged)
RESULT:
Line that fails:
NOTE: I did not find any way to see what class is "not registered".
Expected behavior
App launches, exactly the same as "AppName (Package)" does.
Screenshots
No response
NuGet package version
None
Windows version
Windows 11 (22H2): Build 22621
Additional context
VS Community 2022, 17.11.5