ATL Commerce Pipeline Component Wizard Broken in VC 6 (214832)

MORE INFORMATION

The following files are available for download from the Microsoft Download Center:
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file. This feature is available in the latest service pack for Site Server 3.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:This feature was first included in Site Server 3.0 Service Pack 3.

In order to use the ATL Pipeline Wizard with Visual C++ 6, it is necessary to add the relevant information for the wizard to the registry entries for Visual C++ 6. The AtlWiz.reg file will make these entries for you. To use the .reg file, simply double-click on the file.

The other file included in PipeWiz.exe (other than the readme) is the Commerce.ctl file. Due to limitations of the software used to generate PipeWiz.exe, it is necessary to rename the file CommerceComp.ctl after it is extracted from the .exe. CommerceComp.ctl has been modified slightly to account for differences in the way Visual C++ 6 handles Wizard extensions. This file should replace the copy in the SDK directory (\Microsoft Site Server\SiteServer\Commerce\SDK\Commerce\Samples\ATLWizard\Template\CommerceComp.ctl) and should be copied along with the other template files to "\Program Files\Microsoft Visual Studio\Common\MSDev98\Template\ATL."

The above fix will enable you to add an ATL Commerce Component via the Insert menu of Visual C++ 6.0; however, the generated ATL code must be modified slightly in order for the component to be recognized by the Pipeline editor. Modify the DLL registration code as follows:

static HRESULT WINAPI UpdateRegistry(BOOL bRegister)
{
//HRESULT hr = _Module.UpdateRegistryClass(GetObjectCLSID(), _T("PipelineTest.PTest.1"), _T("PipelineTest.PTest"), IDS_PROJNAME, THREADFLAGS_BOTH, bRegister);
HRESULT hr = _Module.UpdateRegistryFromResourceD(IDR_PTEST, TRUE, NULL);