EnhEvent.onefile

[This is preliminary documentation and subject to change.]

The onefile property indicates whether to transmit the file and its dependencies as a single cabinet file.

Syntax

object.onefile [ = lonefile ]

Parts

object: Object expression that resolves to an EnhEvent object.
lonefile: Long that indicates whether to transmit the file and all its dependencies as a single file. If this value is non-zero, the file and dependencies are transmitted together in a cabinet file. If it is zero, they are not.

Remarks

You can use onefile to ensure that dependency files are downloaded with their base page.

If onefile is True when the stream is converted to low-level format, the stream compiler objects automatically add events to the stream that package the file and its dependencies into a cabinet file, transmit the cabinet file, and unpackage the cabinet file on the client.

Examples

The following adds an event to the stream, specifying onefile to be True.

evs.AddText = "00:00:00.0 trigger(3 ""<Mypage.htm>[targ:MyTarg]"");"
Set e = evs.LastAdd
e.onefile = True

The preceding produces the following enhancement stream language statement.

00:00:00.0 trigger(3 "<Mypage.htm>[targ:MyTarg]") onefile;

If your application converted the event to low-level syntax using EnhEvent.Flatten or EnhEvents.Flatten, the stream compiler objects would package Mypage.htm with its dependencies and replace the preceding high-level event with the following:

before -00:10:00.0 cabfile.cab; 
-00:05:00.0 trigger(1 "<CAB> [bpc://MyShow/cabfile.cab]");
00:00:00.0 trigger(3 "<Mypage.htm>[targ:MyTarg]") only

QuickInfo