Closed mimregit closed 9 months ago
Hi I'm an AI powered bot that finds similar issues based off the issue title.
Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one. Thank you!
Note: You can give me feedback by thumbs upping or thumbs downing this comment.
I think you need to set your EntryPoint to "Windows.FullTrustApplication".
I think you need to set your EntryPoint to "Windows.FullTrustApplication".
That helps, thank you!!
Describe the bug
I created a sample application, there was nothing special, just do it with the wizard, named AppTest. The only modification was to add the appExecutionAlias extension to the package manifest file:
Started the app from the Visual Studio wroked well. Launched a command prompt, and typed in: AppTest
Weird results are:
The Application Object must initially be accessed from the multi-thread apartment. at WinRT.ExceptionHelpers.g__Throw|39_0(Int32 hr)
at WinRT.ExceptionHelpers.ThrowExceptionForHR(Int32 hr)
at ABI.Microsoft.UI.Xaml.IApplicationStaticsMethods.Start(IObjectReference _obj, ApplicationInitializationCallback callback)
at Microsoft.UI.Xaml.Application.Start(ApplicationInitializationCallback callback)
at AppTest.Program.Main(String[] args)
Please, Microsoft, this problem has a predecessor, and I found never a solution on any forum!
At this moment it is impossible to launch from command line any WinUI application, although it would be necessary. How can we solve this problem?
Steps to reproduce the bug
Expected behavior
No response
Screenshots
NuGet package version
WinUI 3 - Windows App SDK 1.4.5: 1.4.240411001
Windows version
Windows 11 (22H2): Build 22621
Additional context
No response