Disclaimer: All the information below was gathered by me personally, without the help or knowledge of the fine folks at SOFO. Because V4 is still in beta, things may change and the following may not work once the final version is released. Use at your own risk.
Well, I've done a little bit of playing around, and here's what I've come up with so far. There is more than just a scripting engine in V4 - there is an entire COM interface - which means that any language that supports COM and .NET can interact with V4.
For example, here's the equivelant of the "simple.vb" script, written in C#:
1. Create a standard C# windows application using .NET
2. Add a reference to "Interop.VegasCOM.dll", which is located in the V4 installation directory
3. Add the following code to the "main" function:
string VersionString = "<Not Set>";
VegasCOMClass VegasApp = new VegasCOMClass();
VegasApp.GetVersionString(ref VersionString);
MessageBox.Show(VersionString);
Note: If V4 is currently running, this works fine. If V4 is not currently running, it will be started automatically by Windows. In this case, however, I am getting an error message from V4 as it starts. I haven't debugged this yet. Everything else still works.
You can use ILDASM to view inside Interop.VegasCOM.dll and see what functions are provided.
Well, I've done a little bit of playing around, and here's what I've come up with so far. There is more than just a scripting engine in V4 - there is an entire COM interface - which means that any language that supports COM and .NET can interact with V4.
For example, here's the equivelant of the "simple.vb" script, written in C#:
1. Create a standard C# windows application using .NET
2. Add a reference to "Interop.VegasCOM.dll", which is located in the V4 installation directory
3. Add the following code to the "main" function:
string VersionString = "<Not Set>";
VegasCOMClass VegasApp = new VegasCOMClass();
VegasApp.GetVersionString(ref VersionString);
MessageBox.Show(VersionString);
Note: If V4 is currently running, this works fine. If V4 is not currently running, it will be started automatically by Windows. In this case, however, I am getting an error message from V4 as it starts. I haven't debugged this yet. Everything else still works.
You can use ILDASM to view inside Interop.VegasCOM.dll and see what functions are provided.