free .NET ftp, or other network libraries

[John]

Hi,

Is there any good free.NET ftp library other than "edtFTPnet"?
Any good free library equivalent to apache.commons.net.* ?

Thanks for any recommendation.

Regards,
John

 

[Samuel R. Neff]

In .NET 2.0 WebClient and WebRequest.Create() provide FTP
functionality.

HTH,

Sam

 

[=?ISO-8859-1?Q?Arne_Vajh=F8j?=]

Is there any good free.NET ftp library other than "edtFTPnet"?
Any good free library equivalent to apache.commons.net.* ?

FTP is supported in .NET 2.0.

If you are stil on 1.x or has special needs for FTP (the 2.0
FTP is not very cooperative with more exotic FTP servers),
then you will need to find some FTP code.

There are several available on the internet. I have some
code myself that I can post if you are interested.

For complete libraries there are a bunch of commercial libs:
http://www.rebex.net/default.aspx
http://www.chilkatsoft.com/ftp-2-dotnet.asp
http://www.jscape.com/sftpdotnet/index.html
etc.etc.

[some of the value they add is support for secure
FTP connections]

I have not seen a port of commons net to .NET !

Arne

 

[Samuel R. Neff]

I would add that be very careful with free ftp libraries and examples
you find on the internet (including classes provided by a C#
networking book). We tried a few and found that none of them
implemented the FTP spec correctly and we ended up having problems
until we rewrote one ourselves.

If you need a 3rd party library this is one area where I would look
for something that has a lot of support behind it--commercial options
being the best.

HTH,

Sam


------------------------------------------------------------
We're hiring! B-Line Medical is seeking .NET
Developers for exciting positions in medical product
development in MD/DC. Work with a variety of technologies
in a relaxed team environment. See ads on Dice.com.

Is there any good free.NET ftp library other than "edtFTPnet"?
Any good free library equivalent to apache.commons.net.* ?

FTP is supported in .NET 2.0.

If you are stil on 1.x or has special needs for FTP (the 2.0
FTP is not very cooperative with more exotic FTP servers),
then you will need to find some FTP code.

There are several available on the internet. I have some
code myself that I can post if you are interested.

For complete libraries there are a bunch of commercial libs:
http://www.rebex.net/default.aspx
http://www.chilkatsoft.com/ftp-2-dotnet.asp
http://www.jscape.com/sftpdotnet/index.html
etc.etc.

[some of the value they add is support for secure
FTP connections]

I have not seen a port of commons net to .NET !

Arne

 

[=?ISO-8859-1?Q?Arne_Vajh=F8j?=]

I would add that be very careful with free ftp libraries and examples
you find on the internet (including classes provided by a C#
networking book). We tried a few and found that none of them
implemented the FTP spec correctly and we ended up having problems
until we rewrote one ourselves.

If you need a 3rd party library this is one area where I would look
for something that has a lot of support behind it--commercial options
being the best.

Hm.

I would argue the other way around.

Some source code you find you can fix. With a commercial
implementation you are dependent on the vendors will
to fix the problem.

Arne

 

[Samuel R. Neff]

I never really understood that argument about open source. Wouldn't
most developers rather spend time writing their own software than
fixing the open source stuff they use?

Now of course there is a lot of great open source software out there
and having the code is great if you want to make enhancements or need
to debug interaction between the 3rd party code and your code.

However, in the particular area discussed here, I've found that the
examples we tried did not work in many situations and thus I'm am
advising caution. Sorry I can't be more specific.

Sam

 

[=?ISO-8859-1?Q?Arne_Vajh=F8j?=]

I never really understood that argument about open source. Wouldn't
most developers rather spend time writing their own software than
fixing the open source stuff they use?

Ofcourse.

But they will also rather spend a day or two fixing the bug
in the open source than waiting 2 years for the commercial
vendor to fix the bug.

Arne

 

[Jon Skeet [C# MVP]]

I never really understood that argument about open source. Wouldn't
most developers rather spend time writing their own software than
fixing the open source stuff they use?

In an ideal world, it just works. However, when code doesn't work, you
can often fix it if it's open source. If it's commercial, you have to
hope that the company you've bought it from is willing to fix the
problem.

I've used a number of open source projects where I've wanted to make
some changes.