----------------------------------------------------------------------------------------------------
2. SUMMARY
----------------------------------------------------------------------------------------------------


This article describes how to implement the IObjectSafety interface in Visual Basic controls to mark the controls safe for scripting and initialization. By default, Visual Basic controls use component category entries in the registry to mark the control safe for scripting and initialization. Implementing the IObjectSafety interface is the preferred method. This article contains all the code that is required to implement this interface in Visual Basic controls.

Please keep in mind that a control should only be marked as safe if it is, IN FACT, SAFE. This means that your control should not contain any malicious code that will be used on the client side. This article does not describe the full details of marking controls as safe for scripting and initialization; it simply demonstrates how to do it in code. Please refer to the Internet Client Software Development Kit (SDK) documentation for a detailed description of this. You may choose the References Section of this Article for more help.