DarranRowe
commented
1 month ago I know these three questions are obvious, however, I have found no reference to this in the report.
- Did you verify that no extra package dependencies were added to the AppxManifest.xml file? The build process takes the project's Package.appxmanifest file and fills in any extra details. Visual Studio checks any NuGet references and add dependencies as needed.
- Did you verify that the directory layout for the unpackaged application was the same as the packaged application? This could be relying on libraries being in the correct location, but the build process only moves things into the correct location as part of the packaging process.
-
Did you check for any extra activation information being added to the package? In these cases, did you check if they were activatable in an unpackaged application? An example of this is actually the C++ projection. C++/WinRT tries very hard to activate a type, even to the point of falling back to looking for namespace named libraries in the application directory and querying them directly. To give an example from Win2D, this registers itself in the AppxManifest.xml file:
//Two methods to attempt to obtain the activation factory for Microsoft.Graphics.Canvas.Effects.BlendEffect winrt::Windows::Foundation::IAsyncAction MainWindow::Click_Click(winrt::IInspectable const &, winrt::RoutedEventArgs const &) { //The runtime class to obtain the activation factory for. constexpr const wchar_t runtime_class_string[] = L"Microsoft.Graphics.Canvas.Effects.BlendEffect"; //Attempt to obtain this via the ABI. //This FAILS in an unpackaged desktop application. HSTRING rs{}; HRESULT hr = WindowsCreateString(runtime_class_string, ARRAYSIZE(runtime_class_string)-1, &rs); com_ptr<::IActivationFactory> af; hr = RoGetActivationFactory(rs, IID_PPV_ARGS(af.put())); WindowsDeleteString(rs); rs = nullptr; //Attempt to obtain this via C++/WinRT //This SUCCEEDS in an unpackaged desktop application. auto af_wrt = winrt::get_activation_factory(runtime_class_string); co_return; }This is using C++, but using the ABI is easier here. The big point is, are you sure that the WinRT objects that are not part of the Windows App Runtime activate properly. If they are registered in the package and they don't, you may need to add the registrations to the application manifest file using registration free WinRT.
I know these are pretty generic questions and observations. But these should be general things to check.
TommiGustafsson-HMP
Describe the bug
Technology stack
Bug
SKGLView crashes the app at runtime when .NET MAUI App is built in the unpackaged mode (
-p:WindowsPackageType=None).Steps to reproduce the bug
dotnet build -f:net9.0-windows10.0.19041.0 -c:Debug -p:WindowsPackageType=None -p:RuntimeIdentifierOverride=win10-x64 -p:WindowsAppSDKSelfContained=truebin\Debug\net9.0-windows10.0.19041.0\win10-x64. The unpackaged app should be there.Expected behavior
App would not crash.
Screenshots
No response
NuGet package version
None
Windows version
No response
Additional context
Relevant log output