Sounds like good news about exception handling improvements.

But very disappointed at the loss of an opportunity to finally implement automated text generation beyond simple presets.

Thanks for the details Edward. I'm just wondering two things...

1) Can you tell me what the disappearance of Interop assembly means?

2) What is your view on version 7 as a scripter? Are you pleased with the changes and additions, or are there things that you expected to see address that haven't been?

Here's a list of scripting changes for Vegas 7:

* It is now possible bypass the missing media dialog(s) when a script
opens a project that contains missing media files. To achieve this,
the script must subscribe to the Vegas object's new MissingMedia
event as shown in the following sample code:

public void OpenProjectWithMissingMedia(Vegas vegas, String projectFile)
{
vegas.MissingMedia += this.HandleMissingMedia;
vegas.OpenProject(projectFile);
}

public void HandleMissingMedia(Object sender, MissingMediaEventArgs args)
{
// to ignore the missing media and leave it offline, set the
// IgnoreMissingMedia property to true.
args.IgnoreMissingMedia = true;
}

The MissingMediaEventArgs also has a MissingMedia property which
tells you the name of the missing media file. However, when the
MissingMedia event is triggered, the project being opened is still
not the active project so you can not get the corresponding Media
object from the MediaPool until after the OpenProject method
returns.


* Scripts can now monitor the progress of a render by subscribing to 3
events prior to calling Vegas's Render method. They are declared as
follows in the Vegas object:

public event EventHandler RenderStarted;
public event RenderStatusEventHandler RenderProgress;
public event RenderStatusEventHandler RenderFinished

The RenderStatusEventHandler delegate is declared as:

public delegate void RenderStatusEventHandler(Object sender, RenderStatusEventArgs args);

And finally the RenderStatusEventArgs object has the following properties:

/// <summary>Get the current status of the render operation.</summary>
public readonly RenderStatus Status;

/// <summary>Get the result code (HRESULT) of the render operation.</summary>
public readonly Int32 Result;

/// <summary>Get the error message string (if any) for the render operation.</summary>
public readonly String ErrorMessage;

/// <summary>Get the percent of the render operation that has completed.</summary>
public readonly Int32 PercentComplete;

For RenderProgress events, the PercentComplete property is the only
relevant property. For RenderFinished events, the Result and
ErrorMessage are only relevant when the Status field is
RenderStatus.Failed. Obviously, scripts should not try to modify
the project in these event handlers.


* Scripts still run in a separate app domain but the script domain is
not unloaded by default after a script runs. This should improve
the user experience by making scripts run faster... especially
precompiled scripts that users run more than once. If you are
developing a precompiled script or one that references precompiled
assemblies, you can force Vegas to unload the script domain setting
the Vegas object's 'UnloadScriptDomainOnScriptExit' property to
true. This will allow you to recompile your assembly without
restarting Vegas. But don't forget to take it out when you release
your script.

* A new property of the Renderer class, SupportsMultichannel,
indicates whether it supports multichannel audio rendering. A new
property of the RenderArgs class, UseChannelMapping, indicates
whether the project's audio channel mappings are used to render a
multichannel media file.

* The PreviewVideoProperties.FullSize property is depricated. Now you
should use the PreviewVideoProperties.PreviewSize property along
with the new VideoPreviewSize enumeration. This allows you to set
the video preview render size to auto, full, half, and quarter.

* Many exceptions thrown within scripting API have been changed to
instances of ApplicationException, ArgumentException, etc.
Previously some exceptions were instances of the Exception base
class.

* Change to the Remove method of various object collections. If the
collection does not contain the specified object, the collection
remains unchanged and no exception is thrown. Previously,
exceptions were thrown for some collection classes. The new
bahavior matches the bahavior of collection classes like
ArrayList. Some exceptions apply such as when you attempt to remove
the root media bin, remove the first envelope point, or remove media
from the media pool when it is still in use.

* Interop assembly (Interop.VegasCOM.dll) is gone.

* Enhanced Render Image Sequence script to allow different file naming conventions and to allow option for files to be overwritten.

* More flexible means of resolving script assembly references.
AssemblyReference elements in script config files may now contain a 'resolver' attribute which indicates where to look for the
referenced assembly. For example:

<ScriptSettings>
<MainClass>TestExtVid</MainClass>
<AssemblyReference resolver="local">Local.dll</AssemblyReference>
<AssemblyReference resolver="appdir">Shared.dll</AssemblyReference>
</ScriptSettings>

The "local" resolver is like the old IsLocal="true" attribute... it
looks for the assembly in the same directory that contains the script.

The "appdir" resolver looks for the assembly in Vegas' install dir.

* New RenderTemplate.Description property allows scripts to get the template's description text.

* overrides for PlugInNode: Equals, GetHashCode, ==, and != operators.

When can we expect to see the Vegas Scripting API documentation (VegasScriptAPI.html) updated with this new information?

Or is it already in an updated version somewhere?

Scripts still run in a separate app domain but the script domain is

Please, how to do that ?
thx