What's needed for MP 1.2 compatibility? (1 Viewer)

[JDWestoby]

OK, read the docs, (looked at the plugin development - still old), nicked someone else's plugin - that was good, trouble was it was C# - oh well!

So in my VS 2008 VB project [HomeSeer plugin] I -
added reference to MP's Common.Utils dll
added the Imports directive (like C#,s using) in AssemblyInfo.vb
added
<Assembly: CompatibleVersion("1.2")>
<Assembly: UsesSubsystem("MP.Config")>

It compiles OK, did whinge about wanting a later version of .NET, stuff it down into the MP plugin directory and fire up a [new install] of MP 1.2 and it comes up as disabled.

What am I missing?

It has GOT to be stupidly simple , pre answer thanks to anyone with the answer

 

[Quarter]

OK, read the docs, (looked at the plugin development - still old), nicked someone else's plugin - that was good, trouble was it was C# - oh well!

So in my VS 2008 VB project [HomeSeer plugin] I -
added reference to MP's Common.Utils dll
added the Imports directive (like C#,s using) in AssemblyInfo.vb
added
<Assembly: CompatibleVersion("1.2")>
<Assembly: UsesSubsystem("MP.Config")>

It compiles OK, did whinge about wanting a later version of .NET, stuff it down into the MP plugin directory and fire up a [new install] of MP 1.2 and it comes up as disabled.

What am I missing?

It has GOT to be stupidly simple , pre answer thanks to anyone with the answer

I think you need to be more specific.

using MediaPortal.Common.Utils;
[assembly: CompatibleVersion("1.1.6.27644")]
[assembly: UsesSubsystem("MP.SkinEngine")]
[assembly: UsesSubsystem("MP.Config")

 

[JDWestoby]

First - thank you for the ridiculously fast reply by the way.

That seems to have done the trick (where is the 'Dummies Guide to MP Development'?).

OK, also found out it may/was copying the old version - doesn't help.

Now enabled - wonderful. I think there are only a few people using this, but I definitely need it!

One question springs to mind, if the version number is SO specific, does this mean I'll have to a) change it for each new MP and b) maintain a list of old versions?

Seems a bit harsh as it doesn't break anything...

 

[Quarter]

First - thank you for the ridiculously fast reply by the way.

That seems to have done the trick (where is the 'Dummies Guide to MP Development'?).

OK, also found out it may/was copying the old version - doesn't help.

Now enabled - wonderful. I think there are only a few people using this, but I definitely need it!

One question springs to mind, if the version number is SO specific, does this mean I'll have to a) change it for each new MP and b) maintain a list of old versions?

Seems a bit harsh as it doesn't break anything...

I'm not a 100% how it's works but you there are a few ways to set it Wiki

 

[JDWestoby]

Idiot's guide

Hy, don't knock it - I could have done with this!

How to make a [VB] plugin 1.2 compatible.

1) Add a reference to MP's Common.Utils.dll
2) In the AssemblyInfo.vb add -
Imports MediaPortal.Common.Utils
<Assembly: CompatibleVersion("1.1.6.27644")>
<Assembly: UsesSubsystem("MP.Config")>
<Assembly: UsesSubsystem("MP.SkinEngine")>

The magic number above seems to be 1.2 Beta specific, hopefully it will change to 1.2 on the official release!

Not too sure if I need both of the UsesSubsytem's (MP has loads defined_ above but doesn't hurt anything.

C# is similar as I originally stloe most of this from another plugin .

Don't forget make any other edits you need and change the version number of course. (Oh come on, no way do you not want to tweak >something<!)

The skin name has changed so make sure you install your skins (if any) to the correct place (from Blue3Wide -> DefaultWide etc.)