Failing to load resources from dynamically loaded assembly

Question

I have a main application, which loads plugins from "./plugins" directory.

The plugins are library assemblies containing UserControls, which use some images (resources).

The problem is that the images are not found when used in the main application.

XamlParseException -> Cannot locate resource 'X.png'

I tried building the resources as "Resource", "Embedded Resource" and "Content", but the exception still persists.

I tried specifying the path to images as

/X.png

and also as (neither works)

pack://application:,,,/<PluginAssemblyName>;X.png

How should I build the image resources so that they are available even after loading the assembly as plugin?

pid · Answer 1 · 2015-04-16T22:16:00.260

1

Have you looked at this example? The Assembly would be the one you've loaded programmatically.

Also take care and make the resource accessible (much like a class is declared public), otherwise it cannot be referenced from outside the assembly.

More about it on MSDN.

edited Apr 16 '15 at 22:16

answered Apr 16 '15 at 16:01

pid

11,472
6
34
63

There is no way to set the image resource as public, or am I missing something? – svecon Apr 16 '15 at 18:59
No, you are not missing something. What I meant was declaring it *accessible* which is *as if* a `class` is made `public`. For images I've added an edit above to explain how to do it, but I guess this is not your concern anymore as you've solved the problem on your own :) – pid Apr 16 '15 at 22:03

score 1 · Answer 2 · answered Apr 16 '15 at 16:28

1

Set the as Resource and try to use the below pack URI syntax. For the resources in the other assembly you should use the /AssemblyName;component syntax

"pack://application:,,,/AssemblyName;component/x.png"

answered Apr 16 '15 at 16:28

Ayyappan Subramanian

5,348
1
22
44

Is there a difference between those two syntaxes? – svecon Apr 16 '15 at 18:59
The difference is your URI type whether is relative or absolute. For more info refer MSDN https://msdn.microsoft.com/en-us/library/aa970069%28v=vs.110%29.aspx – Ayyappan Subramanian Apr 16 '15 at 19:08

score 0 · Answer 3 · answered Apr 16 '15 at 16:20

0

You can use Assembly.GetManifestResourceNames to get a listing of all the resources and the names they have, which will let you know what name(s) to use to retrieve your resource(s).

answered Apr 16 '15 at 16:20

DWright

9,258
4
36
53

I tried this, but the images were not listed there, only "WpfApp.g.resource" and "WpfApp.Properties.Resources.resources". – svecon Apr 16 '15 at 18:58

score 0 · Answer 4 · edited May 23 '17 at 12:28

0

Found an answer to my problem here: https://stackoverflow.com/a/2416464/2649340

In the plugin assembly I use this path to reference the image resource

"/«YourAssemblyName»;component/«YourPath»/«YourImage.png»"

and even while this plugin is loaded in another assembly, it loads correctly.

edited May 23 '17 at 12:28

Community

1
1

answered Apr 16 '15 at 18:55

svecon

554
1
5
8

Failing to load resources from dynamically loaded assembly

4 Answers4