Comet.exe options - Revision history

Barb at 21:31, 8 November 2011

2011-11-08T21:31:19Z

← Older revision		Revision as of 21:31, 8 November 2011
Line 16:		Line 16:
	Once you've setup the CometUserFiles.dat file all you need to do is put the files to be copied in the Comet executables folder on your server (the same folder where you created CometUserFiles.dat).		Once you've setup the CometUserFiles.dat file all you need to do is put the files to be copied in the Comet executables folder on your server (the same folder where you created CometUserFiles.dat).

-	Here's an example of how to specify a required ~~file called MyApp.dll~~:	+	Here's an example of how to specify two required files:

	[Required]		[Required]
	MyApp.dll		MyApp.dll
		+	MyOtherApp.dll

	This option is available to Comet16 and Comet32 installations beginning in Comet 2011 version .449		This option is available to Comet16 and Comet32 installations beginning in Comet 2011 version .449

Barb at 21:29, 8 November 2011

2011-11-08T21:29:30Z

← Older revision		Revision as of 21:29, 8 November 2011
Line 1:		Line 1:
-	Comet.exe should be the target of your Comet shortcut. Located in the Comet executables folder on your server, it is responsible for copying all the files required for loading Comet to the user's workstation and then starting the process of running Comet. The files copied consist of .exes, .dlls, and .ddls. In addition you may specify some of your own files to be copied. The location of these files can be accessed using the $(.EXE.) alias at runtime.	+	Comet.exe should be the target of your Comet shortcut. Located in the Comet executables folder on your server, it is responsible for copying all the files required for loading Comet to the Windows temp folder on the user's workstation and then starting the process of running Comet from there. The files copied consist of .exes, .dlls, and .ddls. In addition you may specify some of your own files to be copied. The location of these files can be accessed using the $(.EXE.) alias at runtime.

-	To make use of this feature, you'll need to create a text file called CometUserFiles.dat in the Comet executables folder. ~~It's~~ records are in .ini format. There are four possible groups of files you may include:	+	To make use of this feature, you'll need to create a text file called CometUserFiles.dat in the Comet executables folder. Its records are in .ini format. There are four possible groups of files you may include:

	[Optional]		[Optional]
Line 13:		Line 13:

	[Required] files are mandatory for Comet to run and must be present in the source folder and will be updated to the target as determined by the timestamp of the files.		[Required] files are mandatory for Comet to run and must be present in the source folder and will be updated to the target as determined by the timestamp of the files.
		+
		+	Once you've setup the CometUserFiles.dat file all you need to do is put the files to be copied in the Comet executables folder on your server (the same folder where you created CometUserFiles.dat).
		+
		+	Here's an example of how to specify a required file called MyApp.dll:
		+
		+	[Required]
		+	MyApp.dll
		+
		+	This option is available to Comet16 and Comet32 installations beginning in Comet 2011 version .449

Barb: Created page with "Comet.exe should be the target of your Comet shortcut. Located in the Comet executables folder on your server, it is responsible for copying all the files required for loading C..."

2011-11-08T21:21:11Z

Created page with "Comet.exe should be the target of your Comet shortcut. Located in the Comet executables folder on your server, it is responsible for copying all the files required for loading C..."

New page

Comet.exe should be the target of your Comet shortcut. Located in the Comet executables folder on your server, it is responsible for copying all the files required for loading Comet to the user's workstation and then starting the process of running Comet. The files copied consist of .exes, .dlls, and .ddls. In addition you may specify some of your own files to be copied. The location of these files can be accessed using the $(.EXE.) alias at runtime.

To make use of this feature, you'll need to create a text file called CometUserFiles.dat in the Comet executables folder. It's records are in .ini format. There are four possible groups of files you may include:

[Optional]
[Required]
[CA Optional]
[CA Required]

Those beginning with CA are for connections to a CometAnywhere host (/Net), otherwise they work the same.

[Optional] files if present in the source folder will be updated to the target folder as determined by the timestamp of the files. If a file is not present in the source folder then any corresponding file at the target will also be deleted.

[Required] files are mandatory for Comet to run and must be present in the source folder and will be updated to the target as determined by the timestamp of the files.