-
Notifications
You must be signed in to change notification settings - Fork 677
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Loaded assembly resources not found #5536
Comments
@alwu-msft FYI |
You saved my bacon I thought I was going to have to write up a defect. I am doing the same thing w/ MEF and getting the same stack trace. Any updated on if and when this will be looked at? WindowsAppSDK version - 1.0.0-experimental |
Verified this is still happening in WindowsAppSDK version - 1.0.0 |
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue still exists in WASDK 1.4 |
With more detailed described here: #6299 |
Describe the bug
Bunch of problems getting loaded assemblies resources when navigating to xaml pages declared on those assemblies.
Steps to reproduce the bug
Steps to reproduce the behavior:
Expected behavior
No problem while navigating or creating pages from those loaded assemblies.
Version Info
NuGet package version:
[WinUI 3 - Windows App SDK 0.8: 0.8.0]
Updated to Windows App SDK 1.0. Still not getting resources.
Uploaded minimal app https://github.com/iomismo/VSMEFTestMainApp
Windows app type:
Additional context
Similar to #3888 and #3657
It is a WinUI module container app which loads different modules through MEF.
MEF composes well and loads all the dlls stored in a "modules" folder inside the main app folder.
Pri files of modules are stored along with dlls files in modules folder.
e.g:
mainapp/modules/module1.dll
mainapp/modules/module1.pri
xbf of modules are stored inside main app folder under its respective Module folder.
e.g.:
mainapp/module1/views/page.xbf
The only way that almost works is in managed only mode and creating instances of that page types through Activator.CreateInstance and assign them to frame.content, but it seems that it (managed) ignores resourcemap not found errors and let you create the page, but without displaying x:uid string resources in the controls, for example. All those string resources are stored in the pri files.
Navigating to a page type through a frame with managed only, throws 'System.AccessViolationException' Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Different behaviors depending on debug mode (sorry for non english words):
Managed and native with Activator.CreateInstance()
Callstack
Output
Managed and native with Frame.Navigate()
Frame.Navigate(pageType
Callstack
Output
Managed only with Frame.Navigate()
Frame.Navigate(pageType
Callstack
Output
Disabling winrt:hresult_error does not work for me.
namedresource uri problem?
This a section of a module pri file. Those namedresources are not being displayed/parsed by xaml page.
Debug does not provides what namedresource is looking for when throwing the error (in native or mixed mode), any idea how to get it?
Thanks!
The text was updated successfully, but these errors were encountered: