Reply to thread

Message

Thanks - that did get me on the right track, especially since it made me realise that they're being loaded (very reasonably) by scanning a given directory for dlls rather than some registry thing or other config store. I'll just note a couple of things here in case it helps anyone else:
* You need to build Filters.sln in Release before running the "Copy Filters to MP Debug[...]" batch, since it explicitly looks in Release folders
* Once those steps are done, invoking Configuration.exe in the debugger directly from VS2013 won't let it see the dlls, because it's not looking in the right directory, i.e. it's looking in mediaportal\Configuration\bin\Debug rather than mediaportal\MediaPortal.Application\bin\Debug. Making it launch in a different working directory won't help, since MediaPortal.Configuration.Config.Config() uses AppDomain.CurrentDomain.BaseDirectory not Environment.CurrentDirectory. (Easiest option for launching from scratch: change that temporarily.)
So now I get the plugins needed when I launch Configuration.exe, and I can get it to confirm it connects to the TV server ok. Still got a problem with MP itself; when I select the 'TV' option, it just stays on the main screen ... but the 'hyperlink' handler associated with that menu option seems to think it should jump to a window with id 1, which doesn't sound right ... so I'm guessing some initial dll load/scan window fixup isn't working for some reason . Will look into that and post in separate thread if needs be ...

<blockquote data-quote="kevin-f" data-source="post: 1158316" data-attributes="member: 155325">Thanks - that did get me on the right track, especially since it made me realise that they're being loaded (very reasonably) by scanning a given directory for dlls rather than some registry thing or other config store. I'll just note a couple of things here in case it helps anyone else:* You need to build Filters.sln in Release before running the &quot;Copy Filters to MP Debug[...]&quot; batch, since it explicitly looks in Release folders* Once those steps are done, invoking Configuration.exe in the debugger directly from VS2013 won't let it see the dlls, because it's not looking in the right directory, i.e. it's looking in mediaportal\Configuration\bin\Debug rather than mediaportal\MediaPortal.Application\bin\Debug. Making it launch in a different working directory won't help, since MediaPortal.Configuration.Config.Config() uses AppDomain.CurrentDomain.BaseDirectory not Environment.CurrentDirectory. (Easiest option for launching from scratch: change that temporarily.)So now I get the plugins needed when I launch Configuration.exe, and I can get it to confirm it connects to the TV server ok. Still got a problem with MP itself; when I select the 'TV' option, it just stays on the main screen ... but the 'hyperlink' handler associated with that menu option seems to think it should jump to a window with id 1, which doesn't sound right ... so I'm guessing some initial dll load/scan window fixup isn't working for some reason . Will look into that and post in separate thread if needs be ...</blockquote>

[QUOTE="kevin-f, post: 1158316, member: 155325"] Thanks - that did get me on the right track, especially since it made me realise that they're being loaded (very reasonably) by scanning a given directory for dlls rather than some registry thing or other config store. I'll just note a couple of things here in case it helps anyone else: * You need to build Filters.sln in Release before running the "Copy Filters to MP Debug[...]" batch, since it explicitly looks in Release folders * Once those steps are done, invoking Configuration.exe in the debugger directly from VS2013 won't let it see the dlls, because it's not looking in the right directory, i.e. it's looking in mediaportal\Configuration\bin\Debug rather than mediaportal\MediaPortal.Application\bin\Debug. Making it launch in a different working directory won't help, since MediaPortal.Configuration.Config.Config() uses AppDomain.CurrentDomain.BaseDirectory not Environment.CurrentDirectory. (Easiest option for launching from scratch: change that temporarily.) So now I get the plugins needed when I launch Configuration.exe, and I can get it to confirm it connects to the TV server ok. Still got a problem with MP itself; when I select the 'TV' option, it just stays on the main screen ... but the 'hyperlink' handler associated with that menu option seems to think it should jump to a window with id 1, which doesn't sound right ... so I'm guessing some initial dll load/scan window fixup isn't working for some reason . Will look into that and post in separate thread if needs be ... [/QUOTE]