By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
464,760 Members | 1,091 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 464,760 IT Pros & Developers. It's quick & easy.

FTP with VB6.0 vs VB.NET

P: n/a
In VB 6.0 I could upload a local file to the mainframe and specify in the VB statement both the local file name and the name to assign to the file when it was created on the mainframe.

Can I do this same thing with VB.NET? It seems that the only available FTP command is the 'STOR' and it looks like that just uploads the file to the mainframe with the same name it had locally.

From http://www.developmentnow.com/g/38_0...anguages-vb.ht

Posted via DevelopmentNow.com Group
http://www.developmentnow.com
Nov 21 '05 #1
Share this Question
Share on Google+
5 Replies

P: n/a
JGPa<no****@developmentnow.com> wrote in
news:17**********************************@msnews.m icrosoft.com:
In VB 6.0 I could upload a local file to the mainframe and specify in
the VB statement both the local file name and the name to assign to
the file when it was created on the mainframe.

Can I do this same thing with VB.NET? It seems that the only
available FTP command is the 'STOR' and it looks like that just
uploads the file to the mainframe with the same name it had locally.


Yes.

http://www.indyproject.org/

Its free, supports VB.NET and allows you to upload using a different file name on the server than
exists locally.

You can ask in their newsgroups for sample code if you have trouble.
--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"

Make your ASP.NET applications run faster
http://www.atozed.com/IntraWeb/
Nov 21 '05 #2

P: n/a
And if you want more capabilities/features, great documentation, and
prompt support whenever you need it, try Xceed FTP for .NET.

It also does SSL and works with many types of FTP servers.

http://www.xceedsoft.com/products/ftpnet

On Thu, 21 Jul 2005 21:52:40 +0300, "Chad Z. Hower aka Kudzu"
<cp**@hower.org> wrote:
JGPa<no****@developmentnow.com> wrote in
news:17**********************************@msnews. microsoft.com:
In VB 6.0 I could upload a local file to the mainframe and specify in
the VB statement both the local file name and the name to assign to
the file when it was created on the mainframe.

Can I do this same thing with VB.NET? It seems that the only
available FTP command is the 'STOR' and it looks like that just
uploads the file to the mainframe with the same name it had locally.


Yes.

http://www.indyproject.org/

Its free, supports VB.NET and allows you to upload using a different file name on the server than
exists locally.

You can ask in their newsgroups for sample code if you have trouble.


--
Alex Leblanc
Xceed Software Inc.
http://www.xceedsoft.com

Check out our advanced .NET zip file and compression library

Email: xL*******@xceedsoft.com (remove the first 'x')
Nov 21 '05 #3

P: n/a
"AlexL [Xceed]" <xL*******@xceedsoft.com> wrote in
news:h5********************************@4ax.com:
And if you want more capabilities/features, great documentation, and


I think that the more solutions the better, and Im glad you posted another alternative. However you
should be careful about comparing "more capabilities/features" without actualy looking what you
replied to.

I thikn you underestimated what Indy implements and simply tried to one up it. You might want to look
at Indy's FTP support and the number of servers that it supports, including some very odd old
mainframes and miniframes, and so forth.

Of course with a commecial solution you have docs, support and so on. Althougth Indy has
commercial support options as well. :)

--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"

Develop ASP.NET applications easier and in less time:
http://www.atozed.com/IntraWeb/
Nov 21 '05 #4

P: n/a
In article <h5********************************@4ax.com>,
xL*******@xceedsoft.com says...
And if you want more capabilities/features, great documentation, and
prompt support whenever you need it, try Xceed FTP for .NET.

It also does SSL and works with many types of FTP servers.

http://www.xceedsoft.com/products/ftpnet

I hate to get into a "mine is better than yours debate" because it's not
my place to judge your product. Besides, both Commercial and Open
Source projects each have their own merits and I don't care to go into
the Commercial vs. Open Source debate. SOmetimes, an Open SOurce
project may be better than a commercial alternative.

Our FTP client may be more advanced than you would think.

We support quite a number of FTP listing formats. In addition to the
standard Unix and WIndowsNT FTP Service, Indy's FTP client has parsers
for the following:

Bull GCOS 7 or Bull DPS 7000
Bull GCOS 8 or Bull DPS 9000/TA200
Cisco IOS
Distinct FTP Server
EPLF (Easily Parsed List Format)
HellSoft FTP Server for Novell Netware 3 and 4
HP 3000 or MPE/iX including HP 3000 with Posix
IBM AS/400, OS/400
IBM MVS, OS/390, z/OS
IBM OS/2
IBM VM, z/VM
IBM VSE
KA9Q or NOS
Microware OS-9
Music (Multi-User System for Interactive Computing)
NCSA FTP Server for MS-DOS (CUTCP)
Novell Netware
Novell Netware Print Services for UNIX
Stratus VOS
TOPS20
UniTree
VMS or VMS (including Multinet, MadGoat, UCX)
Wind River VxWorks
WinQVT/Net 3.98.15
Xecom MicroRTOS
BayNetworks WfFTP
Tandem NonStop Guardian

We also may be supporting other FTP listing formats but I've lost track.

But there's far more than simply that. Indy 10's FTP client supports
the following specifications:

RFC 959 File Transfer Protocol (FTP)
RFC 1123 Requirements for Internet Hosts -- Application and Support
RFC 2389 Feature negotiation mechanism for the File Transfer Protocol
RFC 2428 FTP Extensions for IPv6 and NATs

We also support the following draft specifications:

draft-murray-auth-ftp-ssl-16.txt - Securing FTP with TLS
draft-ietf-ftpext-mlst-16.txt - Extensions to FTP
draft-preston-ftpext-deflate-03.txt - Deflate transmission mode for FTP

We do also support several informal FTP Extensions such as:

http://www.raidenftpd.com/kb/kb000000037.htm - How to implement FXP
(server to server transfer) over SSL/TLS using SSCN command
XCRC, XMD5, XHSA1
MFMT - specified in "draft-somers-ftp-mfxx-01.txt"

All of this is in addition to FTP Proxy support, Socks support, HTTP
Tunneling proxy support, and One-Time-Only password system. There may
be other stuff we support in that client but I guess I've started to
loose track. I've been working on Indy's FTP client for several years.

As Chad pointed out, there is commercial support available. There is
osme Indy documentation as well. There is also a Knowlege Base that
covers a lot of FTP at http://www.indyproject.org/KB/ and I have
recently started blogging about some of work on Indy.

--
J. Peter Mugaas - Indy Pit Crew
Internet Direct (Indy) Website - http://www.indyproject.org
Check our my blog at
http://www.indyproject.org/Sockets/B...gaas/index.iwp
If I want to do business with you, I will contact you. Otherwise, do
not contact me.
Nov 21 '05 #5

P: n/a
Peter,

That's some feature list indeed. I stand corrected. Its not my place
to judge your product either, my bad. It sounds from your description
like your Open Source solution rises far above most other free
development solutions levels of completeness.

Keep it up!

AL

On Fri, 29 Jul 2005 17:49:20 -0400, J. Peter Mugaas
<om******@mail.wvnet.edu> wrote:
In article <h5********************************@4ax.com>,
xL*******@xceedsoft.com says...
And if you want more capabilities/features, great documentation, and
prompt support whenever you need it, try Xceed FTP for .NET.

It also does SSL and works with many types of FTP servers.

http://www.xceedsoft.com/products/ftpnet

I hate to get into a "mine is better than yours debate" because it's not
my place to judge your product. Besides, both Commercial and Open
Source projects each have their own merits and I don't care to go into
the Commercial vs. Open Source debate. SOmetimes, an Open SOurce
project may be better than a commercial alternative.

Our FTP client may be more advanced than you would think.

We support quite a number of FTP listing formats. In addition to the
standard Unix and WIndowsNT FTP Service, Indy's FTP client has parsers
for the following:

Bull GCOS 7 or Bull DPS 7000
Bull GCOS 8 or Bull DPS 9000/TA200
Cisco IOS
Distinct FTP Server
EPLF (Easily Parsed List Format)
HellSoft FTP Server for Novell Netware 3 and 4
HP 3000 or MPE/iX including HP 3000 with Posix
IBM AS/400, OS/400
IBM MVS, OS/390, z/OS
IBM OS/2
IBM VM, z/VM
IBM VSE
KA9Q or NOS
Microware OS-9
Music (Multi-User System for Interactive Computing)
NCSA FTP Server for MS-DOS (CUTCP)
Novell Netware
Novell Netware Print Services for UNIX
Stratus VOS
TOPS20
UniTree
VMS or VMS (including Multinet, MadGoat, UCX)
Wind River VxWorks
WinQVT/Net 3.98.15
Xecom MicroRTOS
BayNetworks WfFTP
Tandem NonStop Guardian

We also may be supporting other FTP listing formats but I've lost track.

But there's far more than simply that. Indy 10's FTP client supports
the following specifications:

RFC 959 File Transfer Protocol (FTP)
RFC 1123 Requirements for Internet Hosts -- Application and Support
RFC 2389 Feature negotiation mechanism for the File Transfer Protocol
RFC 2428 FTP Extensions for IPv6 and NATs

We also support the following draft specifications:

draft-murray-auth-ftp-ssl-16.txt - Securing FTP with TLS
draft-ietf-ftpext-mlst-16.txt - Extensions to FTP
draft-preston-ftpext-deflate-03.txt - Deflate transmission mode for FTP

We do also support several informal FTP Extensions such as:

http://www.raidenftpd.com/kb/kb000000037.htm - How to implement FXP
(server to server transfer) over SSL/TLS using SSCN command
XCRC, XMD5, XHSA1
MFMT - specified in "draft-somers-ftp-mfxx-01.txt"

All of this is in addition to FTP Proxy support, Socks support, HTTP
Tunneling proxy support, and One-Time-Only password system. There may
be other stuff we support in that client but I guess I've started to
loose track. I've been working on Indy's FTP client for several years.

As Chad pointed out, there is commercial support available. There is
osme Indy documentation as well. There is also a Knowlege Base that
covers a lot of FTP at http://www.indyproject.org/KB/ and I have
recently started blogging about some of work on Indy.

J. Peter Mugaas - Indy Pit Crew
Internet Direct (Indy) Website - http://www.indyproject.org
Check our my blog at
http://www.indyproject.org/Sockets/B...gaas/index.iwp
If I want to do business with you, I will contact you. Otherwise, do
not contact me.

--
Alex Leblanc
Xceed Software Inc.
http://www.xceedsoft.com

Check out our advanced .NET grid and Windows Forms UI controls

Email: xL*******@xceedsoft.com (remove the first 'x')
Nov 21 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.