Post a reply :: Support Forum

Tip: Styles can be applied quickly to selected text.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

fpreich

Re: Powershell: WinSCP.TransferOptions.ResumeSupport

martin wrote:

fpreich wrote:

$transferOptions.ResumeSupport
Property 'ResumeSupport' cannot be found on this object. Make sure that it exists.

You may be using an old version of WinSCP .NET assembly that lacks the TransferOptions.ResumeSupport property. Make sure you have the latest version.

Yes, this helps !
Thanks Martin,
appreciate your great work.
martin

Re: Powershell: WinSCP.TransferOptions.ResumeSupport

fpreich wrote:

$transferOptions.ResumeSupport
Property 'ResumeSupport' cannot be found on this object. Make sure that it exists.

You may be using an old version of WinSCP .NET assembly that lacks the TransferOptions.ResumeSupport property. Make sure you have the latest version.
fpreich

Powershell: WinSCP.TransferOptions.ResumeSupport

Can't find this object in Powershell:

$transferOptions.ResumeSupport
Property 'ResumeSupport' cannot be found on this object. Make sure that it exists.

What's the syntax to set it to TransferResumeSupportState.On ?

Thanks in advance

FP
dialalpha

AH! Thank you Martin. That does it.
dialalpha

Property 'WinSCP.TransferOptions.ResumeSupport' lacks setter

Attempting to use the C# dll to incorporate winscp into an App. According to the documentation, we can configure transfer options by creating a TransferOptions class and setting its ResumeSupport property. However, the error below is what happens when you try that -

Error: Property or indexer 'WinSCP.TransferOptions.ResumeSupport' cannot be assigned to -- it is read only


Examining the class via the object browser reveals that indeed the property doesn't have a setter. (screenshot attached)

I'm using dll version number 1.1.5.4214 and runtime version v2.0.50727

Is this a bug or is it intentional?