If the application you're trying to run is really a. NET application as you say, you may not need to run it in a separate process at all. Instead, you can take advantage of the fact that. NET executables are also assemblies. I don't think Visual Studio will let you reference assemblies that end in.exe, but the command-line compiler will. I would try using the command-line compiler to create a wrapper assembly that simply references the executable assembly, and directly calls its Main method, passing in a string array of any command-line parameters you would normally specify. The exit code, if any, will be an integer return value from the Main method. Then you can simply call your wrapper assembly from your ASP. NET app. Depending on what the executable does, and how much it interacts with the console, this approach may not work at all. But if it does work for your case, it should perform much better than spinning up a separate process.
The following command compiles the Web Application1 application in place, specifying a virtual path for the application: Aspnet_compiler -v / Web Application1 The following command compiles the application in place, specifying a physical path for the application. The slash with the /v switch specifies that the compiler will use the physical path as the root when it resolves application root references (for example, with the tilde (~) operator). Aspnet_compiler –p c:\ Documents and Settings\ Default\ My Documents\ My Web Applications\ Web Application1 –v / The following command compiles the Web Application1 application in place, and the tool adds stack trace information if it must report errors. Aspnet_compiler -v / Web Application1 -errorstack The following command compiles the Web Application1 application for deployment, using the physical directory path. It also adds two attributes to the output assemblies. It uses the -keyfile option to add an Assembly Key File Attribute attribute, which specifies that the Key.sn file contains the public/private key pair information that the tool should use to provide strong names for the generated assemblies. The command also uses the -aptca option to add an Allow Partially Trusted Callers Attribute attribute to the generated assemblies. The compiled Web application is created in the directory c:\application Target. Aspnet_compiler -v / Web Application1 -p c:\ Documents and Settings\ Default\ My Documents\ My Web Applications\ Web Application1 -keyfile c:\ Documents and Settings\ Default\ My Documents\ Key.sn -aptca c:\application Target The following command compiles the Web Application1 application for deployment and update. Aspnet_compiler -v / Web Application1 -p c:\ Documents and Settings\ Default\ My Documents\ My Web Applications\ Web Application1 c:\application Target -u The following command compiles the Web Service2 service under the default metabase path, overwriting.
Download Now