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
MediaPortal 1 Plugins
Changes for MP 1.6.0 - .NET 4 is coming!
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="RoChess" data-source="post: 1037426" data-attributes="member: 18896"><p>What is the best approach then in regards to MPEI?</p><p> </p><p>There are users still stuck on an older version of MediaPortal that do not want to update for whatever reason. If they then update MPEI auto or manually it would break things for them. Now they can manually re-install an older version, but might not be aware of that.</p><p> </p><p>For the pre-release I can compile an MPE1 file and offer this as a manual method, but was just thinking ahead for when the real version goes out.</p><p> </p><p>Now I know MPEI Maker supports scripts and such, so maybe there is an easy way to 'detect' what version of the plugin is required and install the appropriate one, but probably best to not reinvent the wheel if somebody already came up with a nice solution for that. Or is MPEI already smart enough to deal with the situation by specifying minimum requirement for each individual update?</p></blockquote><p></p>
[QUOTE="RoChess, post: 1037426, member: 18896"] What is the best approach then in regards to MPEI? There are users still stuck on an older version of MediaPortal that do not want to update for whatever reason. If they then update MPEI auto or manually it would break things for them. Now they can manually re-install an older version, but might not be aware of that. For the pre-release I can compile an MPE1 file and offer this as a manual method, but was just thinking ahead for when the real version goes out. Now I know MPEI Maker supports scripts and such, so maybe there is an easy way to 'detect' what version of the plugin is required and install the appropriate one, but probably best to not reinvent the wheel if somebody already came up with a nice solution for that. Or is MPEI already smart enough to deal with the situation by specifying minimum requirement for each individual update? [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
Changes for MP 1.6.0 - .NET 4 is coming!
Contact us
RSS
Top
Bottom