Custom Shell Weirdness

[Martin Spence]

Seeking a little guidance / benefit of other's experience. I have a custom
shell and it works just as I would expect with one exception. The shell
looks for 2 xml configurations files (one it will create if it does not
exist). I created the custom shell component with a target directory of
C:\Program File\Custom Shell. I added a the custom shell path to the system
path via a registry entry. However, even with the path the shell cannot
find the configuration files unless they are in the C:\Windows\System32
directory. To my simple mind it is almost like the working directory is
C:\Windows\System32 when the shell is invoked and the path is not getting
passed. Yet... the path must be getting passed otherwise the application
could not work?!?

Anyone have any clues or suggestions as to how I can keep my configuration
files out of the C:\Windows\System32 directory?

Thanks

 

[Dave R.]

Seeking a little guidance / benefit of other's experience. I have a
custom shell and it works just as I would expect with one exception.
The shell looks for 2 xml configurations files (one it will create if
it does not exist). I created the custom shell component with a
target directory of C:\Program File\Custom Shell. I added a the
custom shell path to the system path via a registry entry. However,
even with the path the shell cannot find the configuration files
unless they are in the C:\Windows\System32 directory. To my simple
mind it is almost like the working directory is C:\Windows\System32
when the shell is invoked and the path is not getting passed. Yet...
the path must be getting passed otherwise the application could not
work?!?

Anyone have any clues or suggestions as to how I can keep my
configuration files out of the C:\Windows\System32 directory?

We had a similar thing happen with a custom shell. The problem, of
course, is that the current / working directory and the path to the
executable are two different things. See the Target and Start In fields
of any Windows shortcut. The solution we settled on was to read the
command line used to launch the shell and set that as the working
directory before trying to load any configuration files.

Hope this helps.

Dave