home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Development
General Development (no feature request here!)
CompatibleVersion
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="jameson_uk" data-source="post: 999158" data-attributes="member: 11220"><p>Is your plugin actually dependant on the config application? What would break your plugin if the sub-system changes</p><p><a href="http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/18_Contribute/6_Plugins/Plugin_Related_Changes/1.1.0_to_1.2.0/Version_Compatibility" target="_blank">http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/18_Contribute/6_Plugins/Plugin_Related_Changes/1.1.0_to_1.2.0/Version_Compatibility</a></p><p> </p><p>eg. if it is a window plugin then the a change to the skin engine will break it.</p><p>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 ?)</p><p> </p><p>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</p><p>[code=c#][assembly: CompatibleVersion("1.3.100.0","1.1.6.27644")]</p><p>[assembly: UsesSubsystem("MP.SkinEngine")][/code]</p><p> </p><p>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.</p></blockquote><p></p>
[QUOTE="jameson_uk, post: 999158, member: 11220"] Is your plugin actually dependant on the config application? What would break your plugin if the sub-system changes [url]http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/18_Contribute/6_Plugins/Plugin_Related_Changes/1.1.0_to_1.2.0/Version_Compatibility[/url] 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 [code=c#][assembly: CompatibleVersion("1.3.100.0","1.1.6.27644")] [assembly: UsesSubsystem("MP.SkinEngine")][/code] 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. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
CompatibleVersion
Contact us
RSS
Top
Bottom