B
Brent Stevenson
We have an application that monitors multiple VB.Net executables to ensure
they are still running on a server. When one of the pre-determined
executables
crashes our monitor applications uses the "ShellExecute" command to restart
the application. The VB.Net application uses a config file to store
application settings, it uses the
System.Collections.Specialized.NameValueCollection class to reterieve these
values. Retreival of the values works fine
when the VB.Net application is started from a Batch file, or initated from a
Shortcut, but when initiated using the "ShellExecute" command the values
retrieved have a zero length string, they weren't found. The application is
started so the parameters used in the "ShellExecute" command would appear
correct,
it just doesn't find the Config file using this initiation technique. The
Config file uses the executable_name.exe.config naming format and is stored
in the
same directory as the executable.
Please advise.
Thanks Brent
they are still running on a server. When one of the pre-determined
executables
crashes our monitor applications uses the "ShellExecute" command to restart
the application. The VB.Net application uses a config file to store
application settings, it uses the
System.Collections.Specialized.NameValueCollection class to reterieve these
values. Retreival of the values works fine
when the VB.Net application is started from a Batch file, or initated from a
Shortcut, but when initiated using the "ShellExecute" command the values
retrieved have a zero length string, they weren't found. The application is
started so the parameters used in the "ShellExecute" command would appear
correct,
it just doesn't find the Config file using this initiation technique. The
Config file uses the executable_name.exe.config naming format and is stored
in the
same directory as the executable.
Please advise.
Thanks Brent