You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With module initializers, projection assemblies no longer need to be registered. But projected XAML classes (e.g., MainPage) in the app still do, which requires an explicit registration in the app startup path, like:
public App()
{
WinRT.ComWrappersSupport.RegisterProjectionAssembly(typeof(App).Assembly);
}
Failure to do this results in hard to debug TypeLoadExceptions. The preference for projectionAssemblies in TypeNameSupport.FindTypeByNameCore should be preserved (so that projection types take precedence over app types - a previously reported issue), with a fallback for loaded assemblies so that apps don't have to explicitly register.
The text was updated successfully, but these errors were encountered:
With module initializers, projection assemblies no longer need to be registered. But projected XAML classes (e.g., MainPage) in the app still do, which requires an explicit registration in the app startup path, like:
public App()
{
WinRT.ComWrappersSupport.RegisterProjectionAssembly(typeof(App).Assembly);
}
Failure to do this results in hard to debug TypeLoadExceptions. The preference for projectionAssemblies in TypeNameSupport.FindTypeByNameCore should be preserved (so that projection types take precedence over app types - a previously reported issue), with a fallback for loaded assemblies so that apps don't have to explicitly register.
The text was updated successfully, but these errors were encountered: