MFC ATL和OCX控件在静态页面可以调用方法，在apache项目中无法调用或报错“对象不支持属性或方法”

我是个新手，对MFC的认识并不深，更不用说这些单独的控件开发了，前段时间，应客户需求，弄了个OCX控件，注册在本地系统中，在本地静态html中可以正确的执行，当放到apache项目中测试的时候，却无法执行，甚至报错：对象不支持属性或方法。纳闷死了，本来就没多少基础，还冒出这样的一个问题，一时间头都大了，于是，在网上找了好多资料，一致都认为是没有实现IObjectSafety接口造成的。在论坛里，虽然有很多这样的说法，但是没看到贴代码的，都不知道往哪贴代码。

今早在网上看了一段代码分析，感觉甚是有用，于是，就照搬上去了，想不到还真的成功了！

在工程中找到 C工程名Ctrl.h的头文件，然后添加包含一个头文件#include <objsafe.h>，在主题函数中，找到DECLARE_DYNCREATE(C工程名Ctrl)，然后在下方添加上如下一段代码：

DECLARE_INTERFACE_MAP()

    BEGIN_INTERFACE_PART(ObjSafe, IObjectSafety)
    STDMETHOD_(HRESULT, GetInterfaceSafetyOptions) (
            REFIID riid,
            DWORD __RPC_FAR *pdwSupportedOptions,
            DWORD __RPC_FAR *pdwEnabledOptions
    );
       
    STDMETHOD_(HRESULT, SetInterfaceSafetyOptions) (
            REFIID riid,
            DWORD dwOptionSetMask,
            DWORD dwEnabledOptions
    );
 END_INTERFACE_PART(ObjSafe);

声明要实现的接口信息。

在工程中找到C工程名Ctrl.cpp源文件，在文件中找到方法：BOOL C工程名Ctrl::C工程名CtrlFactory::UpdateRegistry(BOOL bRegister)，然后在函数上方添加上如下一段代码：

// Interface map for IObjectSafety

BEGIN_INTERFACE_MAP( C工程名Ctrl, COleControl )
 INTERFACE_PART(C工程名Ctrl, IID_IObjectSafety, ObjSafe)
END_INTERFACE_MAP()

/
// IObjectSafety member functions

// Delegate AddRef, Release, QueryInterface

ULONG FAR EXPORT C工程名Ctrl::XObjSafe::AddRef()
{
    METHOD_PROLOGUE(C工程名Ctrl, ObjSafe)
    return pThis->ExternalAddRef();
}

ULONG FAR EXPORT C工程名Ctrl::XObjSafe::Release()
{
    METHOD_PROLOGUE(C工程名Ctrl, ObjSafe)
    return pThis->ExternalRelease();
}

HRESULT FAR EXPORT C工程名Ctrl::XObjSafe::QueryInterface(
    REFIID iid, void FAR* FAR* ppvObj)
{
    METHOD_PROLOGUE(C工程名Ctrl, ObjSafe)
    return (HRESULT)pThis->ExternalQueryInterface(&iid, ppvObj);
}

const DWORD dwSupportedBits =
  INTERFACESAFE_FOR_UNTRUSTED_CALLER |
  INTERFACESAFE_FOR_UNTRUSTED_DATA;
const DWORD dwNotSupportedBits = ~ dwSupportedBits;
 
/
// CStopLiteCtrl::XObjSafe::GetInterfaceSafetyOptions
// Allows container to query what interfaces are safe for what. We're
// optimizing significantly by ignoring which interface the caller is
// asking for.
HRESULT STDMETHODCALLTYPE
 C工程名Ctrl::XObjSafe::GetInterfaceSafetyOptions(
  REFIID riid,
        DWORD __RPC_FAR *pdwSupportedOptions,
        DWORD __RPC_FAR *pdwEnabledOptions)
{
 METHOD_PROLOGUE(C工程名Ctrl, ObjSafe)

 HRESULT retval = ResultFromScode(S_OK);

 // does interface exist?
 IUnknown FAR* punkInterface;
 retval = pThis->ExternalQueryInterface(&riid,
     (void * *)&punkInterface);
 if (retval != E_NOINTERFACE) { // interface exists
  punkInterface->Release(); // release it--just checking!
 }
 
 // we support both kinds of safety and have always both set,
 // regardless of interface
 *pdwSupportedOptions = *pdwEnabledOptions = dwSupportedBits;

 return retval; // E_NOINTERFACE if QI failed
}

/
// CStopLiteCtrl::XObjSafe::SetInterfaceSafetyOptions
// Since we're always safe, this is a no-brainer--but we do check to make
// sure the interface requested exists and that the options we're asked to
// set exist and are set on (we don't support unsafe mode).
HRESULT STDMETHODCALLTYPE
 C工程名Ctrl::XObjSafe::SetInterfaceSafetyOptions(
        REFIID riid,
        DWORD dwOptionSetMask,
        DWORD dwEnabledOptions)
{
    METHOD_PROLOGUE(C工程名Ctrl, ObjSafe)
 
 // does interface exist?
 IUnknown FAR* punkInterface;
 pThis->ExternalQueryInterface(&riid, (void * *)&punkInterface);
 if (punkInterface) { // interface exists
  punkInterface->Release(); // release it--just checking!
 }
 else { // interface doesn't exist
  return ResultFromScode(E_NOINTERFACE);
 }

 // can't set bits we don't support
 if (dwOptionSetMask & dwNotSupportedBits) {
  return ResultFromScode(E_FAIL);
 }
 
 // can't set bits we do support to zero
 dwEnabledOptions &= dwSupportedBits;
 // (we already know there are no extra bits in mask )
 if ((dwOptionSetMask & dwEnabledOptions) !=
   dwOptionSetMask) {
  return ResultFromScode(E_FAIL);
 }       
 
 // don't need to change anything since we're always safe
 return ResultFromScode(S_OK);
}

这样便可解决无法调用或者控件安全性的问题了！O(∩_∩)O