Can someone help me out with the steps to deploy aa 64-bit version of custom pipelines from 32-bit VS 2005. Building the project in ".NET" allows for the framework loader to automatically build to the proper framework installed.
But our custom pipelines do not appear to be registered because they appear as broken legs when viewed via the Pipeline Editor.
I have found no links discussing this issue so any help is much appreciated!
64-bit CS 2007 - Custom Pipelines - Registration/Deployment Process
shettydeepak
I had some discussing about this with our dev and I think I know what the issue maybe. I don't have a X64 system so just take my word
.
It seems that the pipereg is not 64-bit aware, and do the following:
Make sure that you are using 64-bit version of regasm.exe. Run pipereg but with the “Export registration” option. When the reg file is created make sure to run the reg from a 64-bit cmd.exe console or from Explorer directly. This should fix your issue.
Good luck,
-Max
KyentC
Ryan,
If you are looking for an alternative I've thrown together a PipelineCategoryAttribute and Installer class that allows you to register your components using InstallUtil.exe. Check out PipelineComponents/Shared/PipelineCategoryAttribute.cs in my sample pipeline component.
Cheers,
Colin
Simon Bowles UK
Did you use the pipeline componenet registration on the x64 system
-Max
tnichols333
Erl,
Try checking the registry under HKCR\CLSID\{your component GUID} to see if the Implemented Categories contains a few keys underneath it. If it does, what are those keys
Cheers,
Colin
K. Murli Krishna
PJBM
Max,
Our custom components appeared to be broken because we were using the 32-bit pipeline editor to view pipelines with 64-bit components. When we open the pipeline in the 64-bit editor, then our components appear fine. The issue we have now is that our custom components do not appear in the list of available components when we try to add a component to an existing stage in the pipeline. The list displays several "<unknown>" options and then the rest are standard commerce components. We did register our components with pipereg and made the compents availabe to all stages.
Ryan
S.Sriram
Colin,
I'm working with Erl on the pipeline component issue. I checked the registry for one of our custom components and the implemented categories contained one key underneath it "{62C8FE65-4EBB-45e7-B440-6E39B2CDBF29}".
Ryan
Cryton
That solved the problem. We're able to add our components to the pipeline now. Thanks for your help on this.
-Ryan
DiasVFX
Try and test something you may have already done so. What happens if you create a brand new pipeline file (empty.pcf) then add one of your component, and save it. Then try to open it again and see if you notice the same broken link.
-Max