CompatibleVersion (1 Viewer)

[motey]

Hey guys,
i dont get it!
Im developing a plugin. Everything fine so far. Its hard to get all informations are needed but achievable. Except the dependencie system. what am i doing wrong?
I have tried following constellations:

[assembly: CompatibleVersion("1.3.100.0","1.1.*")]
[assembly: UsesSubsystem("MP.SkinEngine")]
[assembly: UsesSubsystem("MP.Config")]

[assembly: CompatibleVersion("1.3.100.0","1.1.6.27644")]
[assembly: UsesSubsystem("MP.SkinEngine")]
[assembly: UsesSubsystem("MP.Config")]

[assembly: CompatibleVersion("1.3.100.0","*")]
[assembly: UsesSubsystem("MP.SkinEngine")]
[assembly: UsesSubsystem("MP.Config")]

[assembly: CompatibleVersion("1.3.100.0")]
[assembly: UsesSubsystem("MP.SkinEngine")]
[assembly: UsesSubsystem("MP.Config")]

In the MpeMaker i have following configuration:

And on every installation i get the following dependencie error?

Can somebody explain in simple words how the system is working.
thanks!

 

[seco]

I feel your pain, all of this is a pure nightmare for plugin developer.

 

[vcrapps]

I found that sometimes, the mpe maker gets stuck on a certain Compatible version, and the only way to clear it is to restart the computer, then change the compatible numbers.

 

[Edalex]

try

[assembly: CompatibleVersion("1.1.6.27644")]

without submodules and don't forget to delete and readd dll from mpei maker for applying changes
btw, this

[assembly: CompatibleVersion("1.3.100.0","1.1.6.27644")]
[assembly: UsesSubsystem("MP.SkinEngine")]
[assembly: UsesSubsystem("MP.Config")]

should be okay for 1.4.0 prerelease but will require updates with every version.

 

[jameson_uk]

Is your plugin actually dependant on the config application? What would break your plugin if the sub-system changes
http://wiki.team-mediaportal.com/1_..._Changes/1.1.0_to_1.2.0/Version_Compatibility

eg. if it is a window plugin then the a change to the skin engine will break it.
What version(s) do you want to build your plugin for? Do you want to build something that is compatible with multiple versions (is it actually compatible with those versions ?)

If you do not use any other MP code and it is simply the skin engine and your plugin will work in older versions of MP then you should use

[assembly: CompatibleVersion("1.3.100.0","1.1.6.27644")]
[assembly: UsesSubsystem("MP.SkinEngine")]

This will work for versions up to 1.4 pre-release. The version numbers relate to the API versions not MP versions so if there is nothing that will break skin engine in 1.5 then the version will still be 1.3.100.0. If one of the sub systems you need to define a dependency on does change then you will need to update your plugin but not until then.