Reply to thread

Message

<blockquote data-quote="fforde" data-source="post: 969931" data-attributes="member: 52082">Thanks Volumia, you put me on the right track.&nbsp;When running through the Extension Installer, the Extension Installer sets the working directory for the embedded NSIS installer to the MediaPortal directory (this does not seem to happen when simply double clicking the MPE1 file). This is unrelated to where the file is copied, the Extension installer explicitly sets the working directory regardless of the location of the extracted executable, but this only happens when running through the full UI.&nbsp;The initial working path normally should be harmless, however the format of the paths in MediaPortalDirs.xml are inconsistent. Most directories in this file are specified using absolute path, however the plugin directory is sometimes specified using a relative path. I have no idea why it is setup like this, but it is something we were aware of and tested for.&nbsp;So with a MediaPortal working directory and a relative path to the plugin directory we have a problem. We are running from literally the only place in the system where that relative path would resolve. So the installer saves that to use later as the target directory. Later we change our working path to install other files. We get to the DLLs and try to change to the plugin directory which is stored as a relative path. Because we have changed directories this relative path is now invalid. The plugin can't write the DLLs so the installer fails.&nbsp;So bottom line:<ol>
<li data-xf-list-type="ol">The Extension Installer is inconsistent about the working directory when launching embedded executable.</li>
<li data-xf-list-type="ol">The MediaPortalDirs.xml file for some reason sometimes uses relative paths for some directories.</li>
<li data-xf-list-type="ol">The Moving Pics Installer knows how to deal with #2 but there was a bug that was exposed by #1.</li>
</ol></blockquote>

[QUOTE="fforde, post: 969931, member: 52082"] Thanks Volumia, you put me on the right track. When running through the Extension Installer, the Extension Installer sets the working directory for the embedded NSIS installer to the MediaPortal directory (this does not seem to happen when simply double clicking the MPE1 file). This is unrelated to where the file is copied, the Extension installer explicitly sets the working directory regardless of the location of the extracted executable, but this only happens when running through the full UI. The initial working path normally should be harmless, however the format of the paths in MediaPortalDirs.xml are inconsistent. Most directories in this file are specified using absolute path, however the plugin directory is sometimes specified using a relative path. I have no idea why it is setup like this, but it is something we [B]were[/B] aware of and tested for. So with a MediaPortal working directory and a relative path to the plugin directory we have a problem. We are running from literally the only place in the system where that relative path would resolve. So the installer saves that to use later as the target directory. Later we change our working path to install other files. We get to the DLLs and try to change to the plugin directory which is stored as a relative path. Because we have changed directories this relative path is now invalid. The plugin can't write the DLLs so the installer fails. So bottom line: [LIST=1] [*]The Extension Installer is inconsistent about the working directory when launching embedded executable. [*]The MediaPortalDirs.xml file for some reason sometimes uses relative paths for some directories. [*]The Moving Pics Installer knows how to deal with #2 but there was a bug that was exposed by #1. [/LIST] [/QUOTE]

Verification