Export (0) Print
Expand All

IVsaEngine Interface

Defines the methods and properties that a script engine must support and provides programmatic access to the script engine.

For a list of all members of this type, see IVsaEngine Members.

[Visual Basic]
<Guid("E0C0FFE1-7eea-4ee2-b7e4-0080c7eb0b74")>
<InterfaceType(ComInterfaceType.InterfaceIsIUnknown)>
Public Interface IVsaEngine
[C#]
[Guid("E0C0FFE1-7eea-4ee2-b7e4-0080c7eb0b74")]
[InterfaceType(ComInterfaceType.InterfaceIsIUnknown)]
public interface IVsaEngine
[C++]
[Guid("E0C0FFE1-7eea-4ee2-b7e4-0080c7eb0b74")]
[InterfaceType(ComInterfaceType::InterfaceIsIUnknown)]
public __gc __interface IVsaEngine
[JScript]
public
   Guid("E0C0FFE1-7eea-4ee2-b7e4-0080c7eb0b74")
 InterfaceType(ComInterfaceType.InterfaceIsIUnknown)
interface IVsaEngine

Remarks

The IVsaEngine interface is the primary interface through which hosts interact with script engines. All script engines must support the properties and methods of the IVsaEngine interface.

Because code persistence is the responsibility of the host, there is no requirement that source code or binaries be persisted to disk. Under normal runtime conditions, the script engines do not write to disk; however, when you are in debug mode, or when you are persisting compiled state, the JScript .NET engine temporarily stores some files in the temporary directory (or Debug directory, if it has been set). Nevertheless, debugging and persisting compiled state are, in general, privileged operations, so they should pose no security concern. IVsaEngine This persistence scheme helps ensure security, as it enables the condition wherein FileIOPermission is not required for the script engine.

Requirements

Namespace: Microsoft.Vsa

Platforms: Windows 98, Windows NT 4.0, Windows Millennium Edition, Windows 2000, Windows XP Home Edition, Windows XP Professional, Windows Server 2003 family

Assembly: Microsoft.Vsa (in Microsoft.Vsa.dll)

See Also

IVsaEngine Members | Microsoft.Vsa Namespace | IVsaPersistSite

Show:
© 2014 Microsoft