DLLs favailable for 64bit Windows? (General questions)

Hello,
I just started looking at the possibility of using your SSH
DLLs with one of our apps. The app ships both 32 and 64bit
versions for XP and Vista. Are there pre-compiled DLLs for
x64 mode? If not, would I be able to build them from a source
code license?

Thanks.

Hi Frank,

wodSSH ActiveX component and wodSSH.NET component are build in 32bit environment but it should work in 64bit platforms on Windows XP and Windows Vista.

Can you try it and let us know how it goes?

Regards,
Drazen

Hi Frank,

wodSSH ActiveX component and wodSSH.NET component are build in 32bit environment but it should work in 64bit platforms on Windows XP and Windows Vista.

Can you try it and let us know how it goes?

Regards,
Drazen

Hello,
Thanks for the quick response. I am building your VC MFC
example (with fast notifications) as a test case right now. I
am running on Windows XP Pro x64 and Vista x64 Ultimate. If I
build the .exe as a 32bit app ( win32 target), everything works
just fine. If I build the .exe as a 64bit .exe ( x64 target),
I get the following runtime error:

The error comes from the line:

if (!m_SSH.CreateDispatch( WeOnlyDo.wodSSHCom.1 ,NULL)) ...

Under x64, a 64bit .exe cannot load a 32bit DLL, which is
what I think is happening here. If so, do you guys provide
a 64bit DLL? If not, would it be possible for me to build
one if we were to purchase a source code license?

Thanks.

Randal,

our components are written in ATL using VC6 - I don't think VC6 is capable of producing 64bit binaries.

In order to rebuild with VS2005 it is virtually imposible since ATL is quite different.

Isn't tehre any other option to load that DLL?

Kreso

Randal,

our components are written in ATL using VC6 - I don't think VC6 is capable of producing 64bit binaries.

In order to rebuild with VS2005 it is virtually imposible since ATL is quite different.

Isn't tehre any other option to load that DLL?

Kreso

Ah, what I'm running into makes lots of sense now. Your answer is
spot on. One would need to recompile under VS2005 to get a DLL
I can load directly from our app and ATL did change quite a bit so
a simple recompile would not really work for us. I guess our other
option would be to write a stub 32bit app which could access your
DLL and we would open that app with some IPC mechanism...
That was one thing I was were hoping to avoid with your DLL. I
assume you don't have any immediate plans to make the jump to
VS2005 anytime soon?

Thanks.

Randal,

not that easy. Can't you use C# version?

Kreso