Crash when define DISABLE_XAML_GENERATED_MAIN

[shelllet]

when i call TextRecognizer::EnsureReadyAsync() in self-contained app , it throw hresult_access_denied , so i define DISABLE_XAML_GENERATED_MAIN macro and implement main function manuall like this

int __stdcall wWinMain(HINSTANCE, HINSTANCE, PWSTR, int)
{
	auto hr = MddBootstrapInitialize(WINDOWSAPPSDK_RELEASE_MAJORMINOR, nullptr, { 0 });
	if (FAILED(hr))
	{
		auto message = winrt::impl::message_from_hresult(hr);
		::MessageBoxW(NULL, message.c_str(), L"Fatal Error", MB_OK);

		return -1;
	}

	auto cleanup = wil::scope_exit([] { MddBootstrapShutdown(); });

	winrt::init_apartment(winrt::apartment_type::single_threaded);




	::winrt::Microsoft::UI::Xaml::Application::Start(
		[](auto&&)
		{
			::winrt::make<winrt::Simple::implementation::App>();
		});

	return 0;
}

the code executes to ::winrt::Microsoft::UI::Xaml::Application::Start(), a subsequent crash in a self-contained/unpackaged windowsappsdk 1.8.1 c++ app.

[DarranRowe]

You shouldn't be calling MddBootstrapInitialize when the project is set to self contained. MddBootstrapInitialize will attempt to add a reference to the framework version of the Windows App Runtime, not the self contained version.

You shouldn't have to do anything at all for self contained, the build system should automatically be compiling in the necessary initialization files and so the Windows App Runtime should just be usable.

[mominshaikhdevs]

• WCR: ImageDescriptionGenerator yields UnauthorizedAccessException in unpackaged scenarios #5451 (comment).

[adrastogi]

Tagging @dabhattimsft for confirmation of the capability requirement.

[dabhattimsft]

Yes, capability is required for AI apis and app needs to have identity.

[adrastogi]

Thanks @dabhattimsft; this might be a documentation gap then based on what @DrusTheAxe noted when looking at the public docs; would you be able to get those missing pieces filled in?

[dabhattimsft]

Yep tracking: task.ms/59772087