How To IObjectSafety Marks ATL Controls Safe for Initializing (168371)
The information in this article applies to:
- The Microsoft Active Template Library (ATL) 2.0
- The Microsoft Active Template Library (ATL) 2.1
- The Microsoft Active Template Library (ATL) 3.0
This article was previously published under Q168371 SUMMARY
You can use the default implementation of IObjectSafetyImpl to mark a
control as safe for scripting. In many cases, you will also want to mark
the control as safe for initialization.
NOTE: Only mark your control as safe for scripting or initialization if it
really is safe. If the control is potentially unsafe and it is marked as
safe, you may be held liable for damages. See the REFERENCES section below
for more information.
REFERENCES
For additional information about marking ActiveX controls as safe for
scripting and initialization, please see the following articles in the
Microsoft Knowledge Base:
161873
How To Mark MFC Controls Safe for Scripting/Initialization
164119
SAMPLE: Implementing IObjectSafety in an ActiveX control
For in-depth coverage on developing an ActiveX control and deploying it on
the Web, see Paul Johns' article "The ABCs of MFC ActiveX Controls" at:
For topics relevant to this discussion see his companion article "Signing
and Marking ActiveX Controls" at:
(c) Microsoft Corporation 1997, All Rights Reserved.
Contributions by Shawn W. Karr, Microsoft Corporation
Modification Type: | Minor | Last Reviewed: | 7/1/2004 |
---|
Keywords: | kbCtrl kbhowto kbInprocSvr KB168371 |
---|
|