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
Improvement Suggestions
some thoughts about Area 51 testing
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="arion_p" data-source="post: 974439" data-attributes="member: 45945"><p>Having MP load some files from an alternate location can be very hard, depending on which file you want in this alternate location. A lot of files/assemblies are being referenced directly and MP itself has no control (although it could inject its own assembly resolver/loader). Still, some patches change MediaPortal.exe itself, so you would have to start MP from a different folder. All in all it is too complex and error prone.</p><p> </p><p>A much simpler and safer solution would be to allow multiple installations of MP in different folders. This way you can have a production installation and several testing installations. Area51 patches would then be full installers, so testing is consistent. Each installation would ofc use it own data (separate config, databases etc). The only issue with this (or any other similar solution) is DX filters that are registered. This can be solved in two ways:</p><ol> <li data-xf-list-type="ol">Have MP register all its filters on start-up </li> <li data-xf-list-type="ol">Have a batch file to register the filters (belonging to the same installation as the batch file)</li> </ol><p>1st option is fully automatic, but will slow down start up. 2nd option is manual and can result in unreliable test results.</p></blockquote><p></p>
[QUOTE="arion_p, post: 974439, member: 45945"] Having MP load some files from an alternate location can be very hard, depending on which file you want in this alternate location. A lot of files/assemblies are being referenced directly and MP itself has no control (although it could inject its own assembly resolver/loader). Still, some patches change MediaPortal.exe itself, so you would have to start MP from a different folder. All in all it is too complex and error prone. A much simpler and safer solution would be to allow multiple installations of MP in different folders. This way you can have a production installation and several testing installations. Area51 patches would then be full installers, so testing is consistent. Each installation would ofc use it own data (separate config, databases etc). The only issue with this (or any other similar solution) is DX filters that are registered. This can be solved in two ways: [LIST=1] [*]Have MP register all its filters on start-up [*]Have a batch file to register the filters (belonging to the same installation as the batch file) [/LIST] 1st option is fully automatic, but will slow down start up. 2nd option is manual and can result in unreliable test results. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
Improvement Suggestions
some thoughts about Area 51 testing
Contact us
RSS
Top
Bottom