The error is a C# programming error, you pass 6 typed parameters to the DocumentObj25 WCF proxy class, function CheckOut. And the .NET Framework runtime states that there is no CheckOut function that uses these 6 typed parameters in this order.

I opened up Visual Studio and saw that you need an in between structure.

-Dave

Hi Dave,

Thanks for the guidance. Unfortunately, I don't know anything about the inbetween structure (I don't have VS). I'm trying to follow the documentation here: https://docs.rws.com/801922/69001/sdl-tridion-docs-13-sp2/documentobj-2-5--checkout but the inbetween structure isn't mentioned.

All I really want to do is check out a topic, run some XSLT against it, then check it back in. I'd do that with ISHremote, but I can't see how to do it there either. Is there any sample code available that I can look at?

If it really is an automated (fast) process then I would skip the Checkout/Checkin phase... Checkout/Checkin - or some people like to call it Lock/Unlock - is something user oriented.

I think in your scenario you can be a lot more optimistic. So your scenario looks quite pessimistic expecting concurrancy, doing a Checkout and potentially doing error handling if somebody else already has the Lock (read Checkout). In an optimistic scenario, you just download (Get-IshDocumentObjData) and update (Set-IshDocumentObj)... where if you run ISHRemote as a non-Administrator user you will not be allowed to update locked/checked out content. If you are running as Administrator then that update would even be succesfull (but probably not wanted).

Have a look at the Set-IshDocumentObj -FileContent test line 328 in github.com/.../SetIshDocumentObj.Tests.ps1

If it really is an automated (fast) process then I would skip the Checkout/Checkin phase... Checkout/Checkin - or some people like to call it Lock/Unlock - is something user oriented.

I think in your scenario you can be a lot more optimistic. So your scenario looks quite pessimistic expecting concurrancy, doing a Checkout and potentially doing error handling if somebody else already has the Lock (read Checkout). In an optimistic scenario, you just download (Get-IshDocumentObjData) and update (Set-IshDocumentObj)... where if you run ISHRemote as a non-Administrator user you will not be allowed to update locked/checked out content. If you are running as Administrator then that update would even be succesfull (but probably not wanted).

Have a look at the Set-IshDocumentObj -FileContent test line 328 in github.com/.../SetIshDocumentObj.Tests.ps1

LOL. Thanks Dave. Sometimes Mica's scenarios are pessimistic. I spend time cheering him up.

:-)