40

I need to call a VBScript file (.vbs file extension) in my C# Windows application. How can I do this?

There is an add-in to access a VBScript file in Visual Studio. But I need to access the script in code behind. How to do this?

0

5 Answers 5

72

The following code will execute a VBScript script with no prompts or errors and no shell logo.

System.Diagnostics.Process.Start(@"cscript //B //Nologo c:\scripts\vbscript.vbs");

A more complex technique would be to use:

Process scriptProc = new Process();
scriptProc.StartInfo.FileName = @"cscript"; 
scriptProc.StartInfo.WorkingDirectory = @"c:\scripts\"; //<---very important 
scriptProc.StartInfo.Arguments ="//B //Nologo vbscript.vbs";
scriptProc.StartInfo.WindowStyle = ProcessWindowStyle.Hidden; //prevent console window from popping up
scriptProc.Start();
scriptProc.WaitForExit(); // <-- Optional if you want program running until your script exit
scriptProc.Close();

Using the StartInfo properties will give you quite granular access to the process settings.

You need to use Windows Script Host if you want windows, etc. to be displayed by the script program. You could also try just executing cscript directly but on some systems it will just launch the editor :)

Sign up to request clarification or add additional context in comments.

4 Comments

Will the program calling System.Diagnostics.Process.Start() hang until the process ends, or will it continue on leaving the process to run in the background?
Yes. By default the program will run without waiting for the process to end. However, System.Diagnostics.Process.Start().WaitForExit() will force the calling program to wait for the process to end.
I think the filename has to be the file name. i.e not cscript
Can I pragmatically add "permissions to execute" as well?
6

Another approach is to create a VB.NET Class Library project, copy your VBScript code into a VB.NET Class file, and reference the VB.NET Class Library from your C# program.

You will need to fix-up any differences between VBScript and VB.NET (should be few).

The advantage here, is that you will run the code in-process.

4 Comments

However, I did use the method from @Ilya above - this was an excellent way for me to test that my vbscript and vb.net code was producing the same results.
The differences between VBScript and VB.NET are not only a few
@johnnyontheweb would like to learn more about the magnitude of difference in your experience, do yo have.a list or reference - or more info on your ecperience?
sorry I didn't collected the difference I encountered, so don't have a list - you can start for instance form here github.com/dotnet/vblang/issues/584
4

This is a permissions issue. Your application appPool must be running at the highest permission level to do this in 2008. The Identity must be Administrator.

Comments

3

You mean you try to run a vbs file from C#?

It can be done like running any other program from C# code:

Process.Start(path);

But you have to make sure that it won't ask for anything, and it is running with the command line version of the interpreter:

Process.Start("cscript path\\to\\script.vbs");

Comments

1

For the benefit of searchers, I found this post, which gives a clear answer (esp if you have parameters). Have tested it - seems to work fine.

string scriptName = "myScript.vbs"; // full path to script
int abc = 2;
string name = "Serrgggio";

ProcessStartInfo ps = new ProcessStartInfo();
ps.FileName = "cscript.exe";
ps.Arguments = string.Format("\"{0}\" \"{1}\" \"{2}\"", scriptName, abc, name);
//This will equate to running via the command line:
// > cscript.exe "myScript.vbs" "2" "Serrgggio"
Process.Start(ps);

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.