Open nlogozzo opened 1 year ago
@nlogozzo I don't know if building/running from the commandline is a supported scenario for the WASDK/WinUI3? See these discussions/issues in the platform repo:
I would maybe add a note to the issue with your images? It at least seems like you can run, but there are still issues remaining? I don't think there's anything we can do here from the Toolkit side.
I don't know if building/running from the commandline is a supported scenario for the WASDK/WinUI3?
The issue isn't building and running from command line....it builds and runs just fine
I don't think there's anything we can do here from the Toolkit side.
The only issue is that SettingsCard
toolkit widget isn't displayed correctly when running from commandline as seen from this:
https://user-images.githubusercontent.com/17648453/271800256-cc2761d1-6335-4f5f-b557-e25d38d984ed.png
Whereas from VS it looks correctly like this: https://user-images.githubusercontent.com/17648453/271800250-5ccc0d0c-872a-4a75-9226-a871dcf2513e.png
Every other WinUI widget looks and works correctly, just this one Toolkit widget doesn't. Sorry if that was unclear
Describe the bug
When running an unpackaged WinUI 3 Windows App SDK application via
dotnet build && dotnet run
in a Terminal, WCT SettingsCard widgets do not display correctly.When building and running the app from Visual Studio 2022, the widgets are displayed correctly
Steps to reproduce
Start a new unpackaged WinUI 3/WinAppSDK project and add a
wct:SettingsCard
run the app via the terminal withdotnet build && dotnet run
and see that the SettingsCard is not displayed correctly.Expected behavior
Running from VS 2022:
Screenshots
dotnet build && dotnet run
:Code Platform
Windows Build Number
Other Windows Build number
No response
App minimum and target SDK version
Other SDK version
Windows App SDK 1.4.1
Visual Studio Version
2022
Visual Studio Build Number
No response
Device form factor
No response
Additional context
No response
Help us help you
No, I'm unable to contribute a solution.