Dear Piedmont,

Could you please share me object that you have changed for developing in Nav 5.0?

Many thanks in advance,
TNDinh.

Thanks for the update

nikonjoh wrote:

It looks like piedmont was able to change the source and compile and get the .Net Com to work in Dynamics NAV. I am not so talented in the build/compile department.

Is this the current mod needed to resolve this issue?

Not sure I understand your question. But there was no change in this respect, if that's what you ask.

It looks like piedmont was able to change the source and compile and get the .Net Com to work in Dynamics NAV. I am not so talented in the build/compile department.

Is this the current mod needed to resolve this issue?

Thanks,
nikonjoh

Thanks for your feedback.

piedmont wrote:

Is there a way I can mark the topic as solved?

No, there's not.

Yes - thank you Martin - the methods and properties are now visible :D

Is there a way I can mark the topic as solved?

Did my suggestion work for you?

OK found now - in source code from latest Beta version - https://winscp.net/download/winscp524source.zip/download

Thank you

Thanks for your reply Martin.

RE: source code for the .NET assembly - is this the main source download, i.e. https://winscp.net/download/winscp517source.zip/download ?

I could't find a link to source code specific to the .NET assembly...

Kind regards
Piedmont

WinSCP .NET assembly has late binding interface, if that's what you ask about. If you need early binding interface, you can download the assembly source code and change WinSCP.Constants.ClassInterface to ClassInterfaceType.AutoDual.

Hi Martin,

I'm trying to use the COM version of the .NET wrapper. The dev environment is Microsoft Dynamics NAV (a version which supports only COM DLLs)

I've followed the installation instructions in https://winscp.net/eng/docs/library_install

I'm now able to see the DLL as an available variable type. However when i create variables of type 'WinSCP console interface .NET wrapper'.Session or SessionOptions, no methods or properties are visible/available. (The only type which has visible methods is ISessionEvents)

When we develop custom DLLs for Dynamics NAV (in Vis Studio), we have to specify both the DLL and methods to be COM visible - otherwise we get similar behaviour to the above.

Is there anything we can try to resolve this?

Many thanks in advance,
Piedmont

OS: Windows 2003
WinSCP version: 5.1.7.3446