How to pass arguments to child processes without them being treated as relative paths

06/08/2018 Stuart Moore   ID: 330288

Problem

When arguments are passed to a process created under AppAcceleratorV they are treated as relative paths and the current directory will be prepended (unless they are already a full path).

Example

Given the redirection rule

<FileSystem>
   <ExactMatch>
     <From>/original</From>
     <To>/new</To>
   </ExactMatch>
</FileSystem>

When the process running under AppAcceleratorV, ProcessUnderAAV, starts AnotherProcess with arg /original this argument will not be redirected to /new, instead AnotherProcess will start with the argument /original.

Workaround

Add registry redirection rule instead of a file redirection rule.

Example Solution

Given the file redirection rule in the example above, apply the following configuration to the Registry.

<Registry>
  <Redirects>
    <KeyMatch>
       <From>/original</From>
       <To>/new</To>
    </KeyMatch>
  </Redirects>
</Registry>

Source:
Was this article helpful?

Table of Contents

    Can't find what you're looking for?

    Contact Support