If you are creating DTCs to use within Visual InterDev, you can take advantage of the choices published by its environment. The properties for the Environment and State choices are below.
Warning Choices exposed by Visual InterDev DTCs may or may not be carried forward in future versions of the DTC.
Use this choice to determine what environment the DTC is in.
| Member | Value |
| Type | "Environment" |
| Text | "Target Environment" |
| Tags: | |
| BrowserGroup | String representing what browser is targeted. The two possible values are "Generic HTML" and "IE DHTML". |
| ClientLanguage | String representing the default script language that is being targeted on the client. The two possible values are "VBScript" and "JavaScript". |
| ServerLanguage | Same as client |
| TargetEnvironment | String representing what type of page is being targeted. The two possible values are "ASP" and "HTML". |
| DocumentPath | String representing the URL of the page hosting the DTC. If the page is not in a web project the value is NULL. |
| ProjectRoot | String representing the URL of the root of the web project the current page is in. If the page is not in a web project, this value is NULL. |
Use this choice to determine whether or not the Scripting Object Model is enabled for the document. For example, your DTC might generate text that depends on this model. You can detect whether the document can currently support your DTC.
Note DTCs that require the Scripting Object Model are not supported by the FrontPage editor.
| Member | Value |
| Type | "State" |
| Text | "ScriptingObjectModel" |
| Tag Enabled |
True if the scripting object model is enabled for the page; False if it is not. |