We are using the Chilkat libraries for things like mail, FTP and more. I have asked a question in their forum, without reply. Maybe users of Chilkat reading this forum know the answer.
In their download page https://www.chilkatsoft.com/downloads_DotNet.asp you will see that the DLL's come in
32/64 bit versions and/or .Net 4.5/4.6/4.7 versions.
I wonder if there's any real (dis)advantage of using the 4.5 version 32 bits. If they publish the same functionality for all they do not seem to use features from later .Net versions. It safes us changing this line OLEAutoObject{"Chilkat_9_5_0.Ftp2"} (to 9_7_0) a few dozens time. But if someone still has an old .Net version it will keep working. On the other hand, it relies on VC++ 2013 runtime which may be absent on newer systems?
About the 32/64 bit: against a possible performance gain, using a 32 bit version seems to work fine and it will work on all Pc's. Not sure how old a Pc is when it is still 32 bits.
I read some backgound here:
https://www.silabs.com/community/mcu/32 ... _tous-fCrr
Any comments from Chilkat users?
Dick
Chilkat 32/64 bit and/or .Net 4.5/4.6/4.7 version
Chilkat 32/64 bit and/or .Net 4.5/4.6/4.7 version
Hi Dick,
The answer is mentioned in the top of the link that you posted: If you use any library that is 32bit only, then your main app using this library must be 32bit only, too, you can not use a 32bit library from an app that's running as 64bit.
So it all depends if you want to use AnyCPU/x64/x86 platform for your app.
Chris
The answer is mentioned in the top of the link that you posted: If you use any library that is 32bit only, then your main app using this library must be 32bit only, too, you can not use a 32bit library from an app that's running as 64bit.
So it all depends if you want to use AnyCPU/x64/x86 platform for your app.
Chris
Chris Pyrgas
XSharp Development Team
chris(at)xsharp.eu
XSharp Development Team
chris(at)xsharp.eu
Chilkat 32/64 bit and/or .Net 4.5/4.6/4.7 version
Hello Chris,
Dick
Ok, thanks; that answers the 32/64 bit question: one library is called from VO and the other from Vulcan compatible X# so 32 bit it will be. And as none of the changes in Chilkat's release notes (http://cknotes.com/category/release-notes/ if you're interested) are written to be limited to a .Net version>4.5, the library we use for VO can stay on 4.5.Chris wrote:Hi Dick,
The answer is mentioned in the top of the link that you posted: If you use any library that is 32bit only, then your main app using this library must be 32bit only, too, you can not use a 32bit library from an app that's running as 64bit.
Chris
Dick
Chilkat 32/64 bit and/or .Net 4.5/4.6/4.7 version
I use the 32bit .NET component with .NET framework 4.7. I create a COM visible class in C# which is called from a VO generated Automation Server Class. For VO you must use the 32 bit components.
FWIW, I create the .NET COM components to make it easier for me to test and to ease the transition to .NET using whatever .NET language may be use in the future.
Jamal
FWIW, I create the .NET COM components to make it easier for me to test and to ease the transition to .NET using whatever .NET language may be use in the future.
Jamal
Chilkat 32/64 bit and/or .Net 4.5/4.6/4.7 version
Thanks Jamal; I decided to stay on 4.5 but I think either 4.5, 4.6 and 4.7 work equally well.
Dick
Dick