Resolving required plugin assemblies problem

[imilne]

Did you try LoadLibrary before calling any methods that depend ond the DLL?

I haven't had a chance to get back to it. I did come across the following, but I'm not sure if I can get my head around it:

http://blogs.msdn.com/b/jonathanswift/ar...2900_.aspx

I got sidetracked pulling info out of MediaInfo itself, then investigating how to do OSD popups. Need to stop trying to do too many things at once and just concentrate on getting one thing working

[sub]

I haven't had a chance to get back to it. I did come across the following, but I'm not sure if I can get my head around it:

http://blogs.msdn.com/b/jonathanswift/ar...2900_.aspx

Basically, your code would be unchanged except for adding following interop definition in your plugin:

[DllImport("kernel32.dll")]
public static extern IntPtr LoadLibrary(string dllToLoad);


Then in the plugin's constructor, call LoadLibrary("c:\path\to\mediainfo.dll"). Everything else should be unchanged, but it should then be able to find mediainfo.dll when it needs it.

[imilne]

Basically, your code would be unchanged except for adding following interop definition in your plugin

Yep, that's all it needed, thanks! That's one less thing to worry about

Iain

[sub]

great

[mvallevand]

Can something like this be used by a console app to find NUtility and Nshared?

Martin

[sub]

That method will only really help with native code.

Also, if you do have a project that depends on NUtility.dll or NShared.dll, be aware that some of the interfaces from these DLLs only have an implementation in NextPVR.exe, so these things wont function when you use them in some other executable.

[McBainUK]

My plugin is split up in to a number of dlls. Unless all the files are in the Plugins\Common folder I get this error

Any more ideas re this problem?

[sub]

Can you try again with this patch, then post the logs? It logs info about the stack etc, as it tries to match a plugin.

[McBainUK]

Can you try again with this patch, then post the logs?

Here you go.

[sub]

When .net fires an event to say it cant resolve an assembly, it doesnt give me any information about what was trying to load the assembly in the first place, so the app has to try to work it out, otherwise it can only load the assembly from the main application directory. To try working it out, it looks through the current stack to see if it can find a match from the assembly with a loaded plugin. Unfortunately in this case, MusicSpot doesnt appear to be executing anywhere in the current stack, so the app is unable to work it out.