ShellExecuteEx shenanigans?

[eccentric]

I have this C#/.NET code inside isxeq2/innerspace on Windows Vista where strFileName is a string containing the absolute path of a text file:

Code: Select all

try
{
	if (File.Exists(strFileName))
	{
		Program.Log("Shell executing \"{0}\"...", strFileName);

		Process p = new System.Diagnostics.Process();
		p.StartInfo.FileName = strFileName;
		p.StartInfo.UseShellExecute = true;
		p.StartInfo.ErrorDialog = false;

		p.Start();
	}
	else
	{
		Program.Log("Shell execute error: Cannot find file \"{0}\".", strFileName);
	}
}
catch (Exception e)
{
	OnUnhandledException(e);
}

The problem is, after passing the file existence check, the call to Process.Start() throws a "file not found" exception which is clearly bogus. Furthermore, security is not the problem because strFileName is copied verbatim from another string used to open the file from inside my bot at startup.

From what I've been told, Process.Start() is layered on top of the ShellExecuteEx() Win32 function. Does Innerspace have a function hook in place that is botching up the string?

[eccentric]

Oh another thing... I have to do this code from a worker thread because Process.Start() terminates the entire EQ2 process when called from the bot entry point.

[Lax]

I'll check on it, thanks for the details

[eccentric]

Another exception I'm getting is "Not enough storage is available to complete this operation".

The shell execute seems to work ok when client is freshly loaded, but degrades to throwing exceptions after several hours.