NET Framework 1.1 on Vista with sp1 works correctly. Parsing of URL Query Strings in IEExec.exe from. It should not disallow (1) and it should not allow (2). There seems to be a problem with the parsing of URL Query Strings in IEExec.exe from. "Windows will close the program and notify you if a solution is" "A problem caused the program to stop working correctly. "Microsoft IE Execute shell has stopped working " On Windows Vista with Servicepack 1 the following works: (2) and (3) On Windows Vista without Servicepack 1 the following works: (1) and (2) (I did not try (3) and (4)) (1) %systemroot%\Microsoft.NET\Framework\v7\IEEXec.exe " (2) %systemroot%\Microsoft.NET\Framework\v7\IEEXec.exe " (3) %systemroot%\Microsoft.NET\Framework\v\IEEXec.exe " (4) %systemroot%\Microsoft.NET\Framework\v\IEEXec.exe " I believe that (1) and (3) displays correct syntax. The specifik IEExec.exe activations I've used, labled (1).(4) are: Is that true that you will get 'Microsoft IE Execute shell has stopped working' only when you invoke your application.exe or it may happen sometimes If it happens sometimes, you could follow below solution to fix this issue. %systemroot%\Microsoft.NET\Framework\\IEEXec.exe " Note that the "/" has been encoded as "%2F" in the values of p1 and p2. The general form of the IEExec.exe activation from a Command Prompt I use is: The URL with the problematic Query String is parsed to IEExec.exe The syntax I have to use varies depending on whether I use the URL on a Windows Vista OS with- and without Servicepack 1. I have a problem with URL Query Strings containing Windows filepath references of the form /dir1/dir2 etc.
0 kommentar(er)
