Thank you for taking a look with me here.
Some interesting developments and I've attached my Program.cs and PlatformClient.cs files so that you can see what I have going.
While the condition persists where only things in the entry point call and execute their assemblies, I was able to get a successful 'move item from document tray to file cabinet' action by placing an instance of that code into the entry point itself.
This shows that the code works on a basic level (not surprised since it was already in the project...) and that it would probably work if things outside the entry point were calling their assemblies.
You'll find that I've set the access modifiers to public in my Project.cs file for things after the entry point, but really a blind stab that didn't work so I'll be changing those back to their defaults.
Having the code to move from document tray to file cabinet in the entry point works in an experimental way, but carries real problems. For one it seems to be pretty far out from best practices and maybe even more important is a functional limitation where I have to specify the DocID for it to fire off. In the real world I'd need for this to be dynamic and I didn't have any luck bringing the dynamic search elements in the code up into the entry point to deliver full functionality even if the construction was pretty far out from standard.
I really appreciate you taking a look with me and look forward to getting your opinion on what you see.
That's great to know about the rhino docs integration. I know Patrick pretty well.
In this case I built it myself.
The client provided a template CSV file and I built Autoindex routines to populate a dedicated file cabinet where I write the rows for the base invoice and the gl coding detail rows from the table field.
Then i use the sorting order for the result list to arrange and group the rows so that the CSV file that you get when you export the result list conforms to the provided sample.