ATL NT服务运行过程

VC6.0可以自动创建服务，到了2005又到了2010就不可以了，VC6.0健的服务升级也有错，只能自己编写服务类实现。

本文共涉及3个工程：beep、install、uninstall。 1) beep工程用于新服务的实现，工程中包含beep.cpp。编译并生成beep.exe，将其拷贝至c:\目录下，供安装程序调用。当安装完毕后，SCM也将调用beep.exe来执行该服务。 2) install工程用于新服务的安装，工程中包含install.cpp。编译并生成install.exe，将其拷贝至：c:\目录中，然后在Windows NT中单击“开始”，再单击“运行”，使用“运行”命令执行带3个参数的installl.exe程序。输入以下命令行进行安装：c:\install.exe BeepService "Beeper" c:\Beep.exe 。其中BeepService是供SCM内部使用的服务名，Beeper是显示在控制面板的服务程序中的名称，"c:\Beep.exe"是服务所在的可执行文件的路径。安装完毕后，你可以在控制面板的服务程序中看到新增的服务Beeper，点击右键选择“属性”，你就可以设置服务的启动类型、服务的状态和启动参数。 3) uninstall工程用于新服务的卸载，工程中包含uninstall.cpp。编译并生成uninstall.exe，将其拷贝至：c:\目录中，然后在Windows NT中单击“开始”，再单击“运行”，使用“运行”命令执行带1个参数的uninstall.exe程序。输入以下命令行进行卸载：c:\uninstall.exe BeepService。其中BeepService就是在安装服务是生成的供SCM内部使用的服务名。

需要用来获得所需的功能在步骤涉及到 IObjectSafetyImpl 用作您的控件派生的类之一，和重写 GetInterfaceSafetyOptions 和 SetInterfaceSafetyOptions。 这使您实现所需的功能在这种情况下意味着将标记为可安全编写脚本和初始化该控件。 若要将 IObjectSafetyImpl 需要将其添加到您的控件派生的类的列表。 是例如多边形教程中您看到以下： class ATL_NO_VTABLE CPolyCtl : ... public IObjectSafetyImpl // ATL's version of // IObjectSafety { public: BEGIN_COM_MAP(CPolyCtl) ... COM_INTERFACE_ENTRY_IMPL(IObjectSafety) // Tie IObjectSafety // to this COM map END_COM_MAP() STDMETHOD(GetInterfaceSafetyOptions)(REFIID riid, DWORD *pdwSupportedOptions, DWORD *pdwEnabledOptions) { ATLTRACE(_T("CObjectSafetyImpl::GetInterfaceSafetyOptions\n")); if (!pdwSupportedOptions || !pdwEnabledOptions) return E_FAIL; LPUNKNOWN pUnk; if (_InternalQueryInterface (riid, (void**)&pUnk) == E_NOINTERFACE) { // Our object doesn't even support this interface. return E_NOINTERFACE; }else{ // Cleanup after ourselves. pUnk->Release(); pUnk = NULL; } if (riid == IID_IDispatch) { // IDispatch is an interface used for scripting. If your // control supports other IDispatch or Dual interfaces, you // may decide to add them here as well. Client wants to know // if object is safe for scripting. Only indicate safe for // scripting when the interface is safe. *pdwSupportedOptions = INTERFACESAFE_FOR_UNTRUSTED_CALLER; *pdwEnabledOptions = m_dwSafety & INTERFACESAFE_FOR_UNTRUSTED_CALLER; return S_OK; }else if ((riid == IID_IPersistStreamInit) || (riid == IID_IPersistStorage)) { // IID_IPersistStreamInit and IID_IPersistStorage are // interfaces used for Initialization. If your control // supports other Persistence interfaces, you may decide to // add them here as well. Client wants to know if object is // safe for initializing. Only indicate safe for initializing // when the interface is safe. *pdwSupportedOptions = INTERFACESAFE_FOR_UNTRUSTED_DATA; *pdwEnabledOptions = m_dwSafety & INTERFACESAFE_FOR_UNTRUSTED_DATA; return S_OK; }else{ // We are saying that no other interfaces in this control are // safe for initializing or scripting. *pdwSupportedOptions = 0; *pdwEnabledOptions = 0; return E_FAIL; } } STDMETHOD(SetInterfaceSafetyOptions)(REFIID riid, DWORD dwOptionSetMask, DWORD dwEnabledOptions) { ATLTRACE(_T("CObjectSafetyImpl::SetInterfaceSafetyOptions\n")); if (!dwOptionSetMask && !dwEnabledOptions) return E_FAIL; LPUNKNOWN pUnk; if (_InternalQueryInterface (riid, (void**)&pUnk) == E_NOINTERFACE) { // Our object doesn't even support this interface. return E_NOINTERFACE; }else{ // Cleanup after ourselves. pUnk->Release(); pUnk = NULL; } // Store our current safety level to return in // GetInterfaceSafetyOptions m_dwSafety |= dwEnabledOptions & dwOptionSetMask; if ((riid == IID_IDispatch) && (m_dwSafety & INTERFACESAFE_FOR_UNTRUSTED_CALLER)) { // Client wants us to disable any functionality that would // make the control unsafe for scripting. The same applies to // any other IDispatch or Dual interfaces your control may // support. Because our control is safe for scripting by // default we just return S_OK. return S_OK; }else if (((riid == IID_IPersistStreamInit) || (riid == IID_IPersistStorage)) && (m_dwSafety & INTERFACESAFE_FOR_UNTRUSTED_DATA)) { // Client wants us to make the control safe for initializing // from persistent data. For these interfaces, this control // is safe so we return S_OK. For Any interfaces that are not // safe, we would return E_FAIL. return S_OK; }else{ // This control doesn't allow Initialization or Scripting // from any other interfaces so return E_FAIL. return E_FAIL; } } ... } ATL 3.0 中, IObjectSafetyImpl 的实现已更改，使您现在可以作为模板参数提供安全选项。 例如，上述类的声明将显示为 class ATL_NO_VTABLE CPolyCtl : ... public IObjectSafetyImpl { public: BEGIN_COM_MAP(CPolyCtl) ... ，您将不必重写两个方法。 有关其他信息，单击下面，文章编号，以查看 Microsoft 知识库中相应： 192093 PRB： 编译器错误时移植到 ATL 3.0 IObjectSafetyImpl

Windows服务的跟应用程序不同的是可以在windows尚未登陆的情况下一直运行，本例子是实现定时关闭系统服务，使用说明看工程目录下Readme.txt文件