BrowserConfigScriptFlag Property of the IFPCWebBrowserClientConfig Interface
The BrowserConfigScriptFlag property gets a value from the FpcBrowserConfigScriptFlag enumerated type that specifies whether Web browsers running on Forefront TMG Client and Firewall Client computers will use the default automatic configuration script, or a custom automatic configuration script.
C++
HRESULT get_BrowserConfigScriptFlag(
FpcBrowserConfigScriptFlag* pBrowserConfigScriptFlag
);
Parameters
- pBrowserConfigScriptFlag
Pointer to a variable that is set on return to a value from the FpcBrowserConfigScriptFlag enumerated type specifying whether Web browsers running on Forefront TMG Client and Firewall Client computers will use the default automatic configuration script, or a custom automatic configuration script.
Return Value
This property method returns S_OK if the call is successful; otherwise, it returns an error code.
Visual Basic
Property BrowserConfigScriptFlag As FpcBrowserConfigScriptFlag
Property Value
Value from the FpcBrowserConfigScriptFlag enumerated type that specifies whether Web browsers running on Forefront TMG Client and Firewall Client computers will use the default automatic configuration script, or a custom automatic configuration script.
Remarks
This property is read-only. It can be set by calling the SetBrowserConfigScript method. Its default value is fpcBrowserDefaultScript, which indicates that Web browsers running on Forefront TMG Client and Firewall Client computers will use the default automatic configuration script.
Web browsers running on Forefront TMG Client and Firewall Client computers use an automatic configuration script only if the BrowserConfigScriptEnabled property is set to True (VARIANT_TRUE in C++).
Requirements
Client | Requires Windows 7 or Windows Vista. |
Server | Requires Windows Server 2008 R2 or Windows Server 2008 x64 Edition with SP2. |
Version | Requires Forefront Threat Management Gateway (TMG) 2010. |
IDL | Declared in Msfpccom.idl. |
DLL | Requires Msfpccom.dll. |
See Also
Send comments about this topic to Microsoft
Build date: 6/30/2010