Request clarification before answering.
Hi Moshe;
Do you have a specific question?
FWIW: I have used SocketWrench from SocketTools with PB.
Regards ... Chris
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Chris ,
Thanks for responding ( as always , you are very helpful and much much more )
Question :
what is the difference between Library Edition and ActiveX Edition in Socket site ?
As I understand it :
1. Library Edition - working with Dll's ( Declare as Global External Function
and put Dll's in the EXE directory ) and the Functions are ready to use .
2. ActiveX Edition - Use OLE control in your window / User Object and declare + create as needed.
that's it ?
Thanks
Moshe
The library edition requires registration of Callback Functions so that the DLL can notify your application that something has happened. This can be difficult to code for PB where you may need to make custom DLL functions to handle the callbacks.
The ActiveX objects all have events built in, so it's easier to use with an environment like PB.
I really, really can't recommend enough creating a COM wrapped dll in .NET for this kind of stuff. Search Google for Bruce Armstrong's helpful stuff on how to do this. I have a single .NET dll that I call from Powerbuilder to handle all kinds of things from sFTP, SMTP, Outlook, Excel, XML, SharePoint, Encryption and more. I'm no C# programmer but I do know how to find other people's code using Google, and there's a ton of resources out there
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'd say that depends on whether you want to spend your time building your own stuff (which, obviously, gives you complete control) or think your time is worth enough to spend money on other people's stuff (which hopefully is very well debugged and has run into a lot more situations than you might consider!).
I'm in the latter camp. I really like the very affordable Chilkat Software controls, that cover all sorts of things. I currently use it for their SMTP, HTTP/S, and Zip controls.
I agree with you view Dan, but the point is that there are a huge number of Dot Net utilities available that can be easily accessed through the com wrapper, so I'm with Aron on this one.
Having said that, for me the most important thing is how easily it can be maintained for future releases and versions. Sometimes a quick win now causes you a huge amount of pain later when a bought solution with support would not do so.
My rule of thumb is that if it is using standard MS code and options then I'll wrap it in my own code, if its more complex then I'll use someone else's (depending on my QA approving the deployment options too). Happily I do not have to revert to either of these often.
Cheers
David
SocketTools ActiveX Edition has FTP/SFTP/POP/SMTP OCX controls (plus a bunch of others). They have 32/64bit OCXs in the same release, so they're platform independent as well. We've been using them since '97 in PB, VB, and C/C++. They're easy to use, and well supported.
Go here http://sockettools.com/activex-edition-controls/ to see the list of the controls (and descriptions) that come with the ActiveX Edition.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.