Resolving required plugin assemblies problem

[bgowland]

Ok, thanks. I'll get the google pigeons on the case and see what they can find.

You could try hacking the MediaInfoDLL.cs class to use DLLImport with an explicit path which relates to the location of your plugin.

Never tried it but I could walk you through it with some example code that I'd try if I wanted to do something similar.

[imilne]

You could try hacking the MediaInfoDLL.cs class to use DLLImport with an explicit path which relates to the location of your plugin.

Never tried it but I could walk you through it with some example code that I'd try if I wanted to do something similar.

That would be great if you don't mind. I did try messing around with it quickly but the compiler decided it hated me so I gave up for the night.

Iain

[McBainUK]

If you rename the Spotify directory to 'MusicSpot' does it help?

No. Same result.

[bgowland]

That would be great if you don't mind. I did try messing around with it quickly but the compiler decided it hated me so I gave up for the night.

OK, try this...

EDIT to use npvr native call to get data directory (thanks InVermont)

In the plugin class itself add the following (example)...

Code:

public class MyPlugin : SimpleButtonListPlugin
{
    private static string npvrPluginsFolder = "";

    ...

    public override void Activate()
    {
        getNpvrPluginsFolder();
        ...
        base.Activate();
    }

    ...

    private void getNpvrPluginsFolder()
    {
        string npvrDataDirectory = NUtility.SettingsHelper.GetInstance().GetDataDirectory();
        if (!npvrDataDirectory.EndsWith(@"\"))
            npvrDataDirectory += @"\";
        npvrPluginsFolder = npvrDataDirectory + @"Plugins\";
    }

Next, in the MediaInfoDLL.cs class file, add a string for the path to the plugins folder and a new constructor to accept/set the path string (example)...

Code:

public class MediaInfo
{
    private static mediaInfoDLLPath = "";

    // DLLImport stuff here

    public MediaInfo(string dllPath)
    {
            // Add the following line, the rest is the same as the default ctor
            mediaInfoDLLPath = dllPath;

            Handle = MediaInfo_New();
            if (Environment.OSVersion.ToString().IndexOf("Windows")==-1)
                MustUseAnsi=true;
            else
                MustUseAnsi=false;
    }

Finally do a Find/Replace on the MediaInfoDLL.cs file...

Find this...

Code:

[DllImport("MediaInfo.dll")]

Replace with this...

Code:

[DllImport(mediaInfoDLLPath + "MediaInfo.dll")]

If you call the default MediaInfoDLL constructor, then the mediaInfoDLLPath string will be "" so behaviour will be as before but hopefully using the new constructor will allow you to place the MediaInfo.dll in the plugins folder.

No idea if it will work, usual disclaimers, etc, etc.

Cheers,
Brian

[InVermont]

// I couldn't find a method native to N-PVR to get the data folder but
// if there is one, use that.
Brian

NUtility.SettingsHelper.GetInstance().GetDataDirectory()

I think that should do it.

[imilne]

Cheers guys, I'll give it a try tonight if I get the chance...

Iain

[bgowland]

NUtility.SettingsHelper.GetInstance().GetDataDirectory()

I think that should do it.

Indeed it does. I had a feeling there would be a way but didn't spend too much time looking. I'll edit my example to make it a bit more light-weight.

Thanks.

[bgowland]

Cheers guys, I'll give it a try tonight if I get the chance...

Looking slightly cleaner with the NUtility call in there instead of the Reg stuff. Hope it works.

Cheers,
Brian

[imilne]

Stalled at the first attempt unfortunately, with just trying to replace the "MediaInfo.dll" string with the mediaInfoDLLPath variable:

Code:

An attribute argument must be a constant expression, typeof expression or array creation expression of an attribute parameter type

If it needs to be a constant, then I don't see how you can give it something that's got to be dynamic at runtime. Hmm... must be possible somehow.

Iain

[sub]

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