Any ideas on changes required to make an archive pipeline component (that works fine on flat files) work okay on a WCF receive location (for an orchestration published as a web service)?
I tried yesterday, and got strange error about couldn’t load the .DLL (even though I deployed and GACced it).
This morning, it seems to run without error, but no archive row created in my database.
We have some ideas of some other functions we want to put into a pipeline here, so I thought I would start with an existing pipeline.
Thanks,
Neal