wodFtpDLX with source code | WeOnlyDo! SoftwarewodFtpDLX is secure FTP client ActiveX component that supports encrypted and non-encrypted FTP access to the servers for transferring files. It supports old, very common, FTP protocol, but also secured FTPS (FTP+SSL) and SFTP (FTP+SSH). No matter what protocol is selected - it is completely transparent for programming. Same methods and same events apply for all protocols. Together with the component is included Certificate Management Component, you can deal with certificates with ease - assign certificate to be used for client authentication, check validity of remote certificate, etc.
wodFtpDLX with source codewodFtpDLX component is FTP (or, better to say, file-transfer) client component. Not only it provides old fashion FTP protocol, it allows you also to use secured SFTP (Secure-Shell version 2 subsystem, very popular on UNIX), and FTP+SSL protocols as well. Using different protocols is completelly transparent for usage. You have same interface and different protocol - just by changing one property! wodFtpDLX also support client certificate authentication if your server allows/requires it. Besides that - it has its own explorer-like window. You can (with no coding at all!) provide your users direct visual interaction with files and directories on the server.
wodHttpDLX with source code | WeOnlyDo! SoftwareWeOnlyDo Software's wodHttpDLX is a HTTP client ActiveX control that provides easy, both high and low level access to the complete HTTP protocol. It's primary purpose is to retrieve documents and other resources from the WEB. It was designed to be as programmer-friendly as possible. You will find it can be fully automated to get you requested resource, but also can be used by advanced programmers under complete control from your code
wodHttpDLX with source codewodHttpDLX is a HTTP client ActiveX control that provides easy interface to the HTTP protocol. Its primary purpose is to retrieve documents and other resources from the WEB, being as programmer-friendly as possible. You will find it can be fully automated to get you requested resource, but also can be used by advanced programmers under complete control from your code. Supports Proxies, Basic/NTLM authentications, SSL, uploads...
wodAppUpdate with source code | WeOnlyDo! SoftwarewodAppUpdate component should be used by your application to quickly, easily, and securely provide automatic update solution - very popular "check for updates" functionality. This way you increase value and functionality of your product because now your customers always have the most newest version - and you need only 3 lines of code to provide it! wodAppUpdate uses configuration file it finds on the server of your choice (HTTP, HTTPS or FTP) and then determines if local files need to be replaced or not. You can send any additional information via URL to the server - and that way determine if user is allowed to update the application, if he uses regular licensed version etc - using your own server-side scripting. wodAppUpdate doesn't really care what you send and what do you do on the server side.
wodAppUpdate with source codewodAppUpdate component is used to allow your application quickly and easily update itself with latest version, from information found on any kind of WEB or FTP server that you provide. This process is 3-steps easy: CHECK, DOWNLOAD, UPDATE!
wodWebServer.NET with source code | WeOnlyDo! SoftwarewodWebServer.NET is an .NET Component that implements server side of HTTP and HTTPS protocols (HTTPServer). It's main purpose is to serve HTML pages, GIF/JPG/PNG images, documents, and other resources that are accessible through Browser clients (such as Internet Explorer, Mozilla Firefox, Netscape etc..) It is robust, easy to use, fast, and can be used in all .NET environments. It serves both static pages, as well as dynamically created ones. You can run your existing ASPX/ASP.NET pages just with wodWebServer.NET, no need for 3rd party web server, such as IIS. wodWebServer.NET runs through Request/Response objects - whatever client sends is parsed and stored to Request object. When you're ready to deliver response, you just need to populate Response object - such as Body property, StatusCode, and that's it. If you're fast and can do it from within RequestDone event, then you don't even have to call any Send methods - it's delivered automaticaly.
wodWebServer.NET with source codeNative .NET Component that implements server side of HTTP and HTTPS protocols (HTTPServer). Its main purpose is to serve HTML pages, GIF/JPG/PNG images, documents, and other resources that are accessible through Browser clients (such as Internet Explorer, Mozilla Firefox, Netscape etc.)
wodFtpDLX.NET with source code | WeOnlyDo! SoftwarewodFtpDLX.NET is secure FTP client .NET 2.0 (dotnet) component that supports encrypted and non-encrypted FTP access to the servers for transferring files or complete directories. It supports old, very common, FTP protocol, but also secured FTPS (FTP+SSL) and SFTP (FTP+SSH). No matter what protocol is selected - it is completely transparent for programming. Same methods and same events apply for all protocols
wodFtpDLX.NET with source codewodFtpDLX.NET component is FTP (or, better to say, file-transfer) client component. Not only it provides old fashion FTP protocol, it allows you also to use secured SFTP (Secure-Shell version 2 subsystem, very popular on UNIX), and FTP+SSL protocols as well. Using different protocols is completelly transparent for usage. You have same interface and different protocol - just by changing one property! It is written in pure .NET in C#, NET 2.0 framework required to run
|
Categories
All
Archives |