which is better to use?
dim wsh
set wsh = Server.CreateObject("WScript.Shell")
wsh.run "c:uild.exe", 1, True
set wsh = nothing
--or--
Dim Executor
Set Executor = Server.CreateObject("ASPExec.Execute")
Executor.Application = "c:uild.exe"
Executor.ShowWindow = True
Executor.ExecuteWinApp
Set Executor = nothing
I am doing a migration for our web program from IIS 5.0 to IIS 6.0
One thing I was baffled is aspexec component.
I didn't change the code, but it seems the following code doesn't work
anymore in
IIS 6.0 in windows 2003
set Executor = Server.CreateObject("ASPExec.Execute")
Executor.Application = sDosCmd
sResult=Executor.ExecuteDosApp
the sResult actually give "ERROR: Could not create process"
I am building a small Web app that will allow end users to visit a Web page, click a button which will in turn execute a batch file on the Web server which will migrate code from the development environment to QA. The Web app will also capture logins and execution requests, and the batch file currently emails the robocopy log to me.
In researching ways to get the ASP page to execute the batch file, I came across ASPExec from Server Objects - http://www.serverobjects.com/products.htm#free. It seemed straightforward enough, however I have not been able to get the permissions in sync for it to work.
I am trying to run a C compiled executable on the server (this is running on a dedicated box within our network designed for this procedure), that reads from an input file located in the same directory, from an ASP page using ASPExec. The problem is that while I am attempting to do this from the command line, I need to be in the directory where the executable and input file are, since the .exe will read the input file.
Some may say to put the .exe and input in the default, but the .exe and input are in a folder that changes based on the user, therefore you will see the adjustment of the path everytime a user enters the page based on the Session variable "Foldername".
I've tried to open cmd to the directory and run the file sitting in the correct directory, without any success. In short, need to run an .exe (connected to an input file) in a directory that changes based on a user using an ASP page w/ APSExec. Code: