The File Transfer Manager Sucks

  • Thread starter Thread starter clintonG
  • Start date Start date
C

clintonG

That's the title of the suggestion I just left at MSDN Product Feedback
Center [1]. Please login, use that string to find the suggestion I made and
vote for it to support my outrageous demands. If you login, you can read the
whole story why I have gone over the edge and why something must be done
about the File Transfer Manager (FTM).

Briefly, I (we) are agreeing that the FTM is crippleware and needs to
include the ability to report the status of the servers it is attempting to
connect to., i.e. a "demand meter" so to speak. Especially during periods of
heavy demand such as the last two weeks when ASP.NET 2.0 was officially
released.

If you guys don't support me on this I will be forced to write my
congressman and ask for the death penalty.

<%= Clinton Gallagher
METROmilwaukee (sm) "A Regional Information Service"
NET csgallagher AT metromilwaukee.com
URL http://metromilwaukee.com/
URL http://clintongallagher.metromilwaukee.com/


[1] http://lab.msdn.microsoft.com/ProductFeedback/Default.aspx
 
I've never used it and I've written five different apps that use ftp.

I use a native c# class that implements ftp functions using .Net sockets.

It's never failed me yet!
 
One of us is confused.
The File Transfer Manager is what Microsoft loads when we try to download
applications such as Visual Studio 2005 from the MSDN Subscription Downloads
website.

I have an FTP client and I never realized subscriber downloads could be
accessed that way. Are we on the same page?

<%= Clinton Gallagher
METROmilwaukee (sm) "A Regional Information Service"
NET csgallagher AT metromilwaukee.com
URL http://metromilwaukee.com/
URL http://clintongallagher.metromilwaukee.com/


John A. Bailo said:
I've never used it and I've written five different apps that use ftp.

I use a native c# class that implements ftp functions using .Net sockets.

It's never failed me yet!
That's the title of the suggestion I just left at MSDN Product Feedback
Center [1]. Please login, use that string to find the suggestion I made
and vote for it to support my outrageous demands. If you login, you can
read the whole story why I have gone over the edge and why something must
be done about the File Transfer Manager (FTM).

Briefly, I (we) are agreeing that the FTM is crippleware and needs to
include the ability to report the status of the servers it is attempting
to connect to., i.e. a "demand meter" so to speak. Especially during
periods of heavy demand such as the last two weeks when ASP.NET 2.0 was
officially released.

If you guys don't support me on this I will be forced to write my
congressman and ask for the death penalty.

<%= Clinton Gallagher
METROmilwaukee (sm) "A Regional Information Service"
NET csgallagher AT metromilwaukee.com
URL http://metromilwaukee.com/
URL http://clintongallagher.metromilwaukee.com/


[1] http://lab.msdn.microsoft.com/ProductFeedback/Default.aspx
Click to expand...
Click to expand...
 
Oh, ok, I thought it was some c# control thingy.

Yeah, File Transfer Manager sucks, if you say so.

One of us is confused.
The File Transfer Manager is what Microsoft loads when we try to download
applications such as Visual Studio 2005 from the MSDN Subscription Downloads
website.

I have an FTP client and I never realized subscriber downloads could be
accessed that way. Are we on the same page?

<%= Clinton Gallagher
METROmilwaukee (sm) "A Regional Information Service"
NET csgallagher AT metromilwaukee.com
URL http://metromilwaukee.com/
URL http://clintongallagher.metromilwaukee.com/


I've never used it and I've written five different apps that use ftp.

I use a native c# class that implements ftp functions using .Net sockets.

It's never failed me yet!
That's the title of the suggestion I just left at MSDN Product Feedback
Center [1]. Please login, use that string to find the suggestion I made
and vote for it to support my outrageous demands. If you login, you can
read the whole story why I have gone over the edge and why something must
be done about the File Transfer Manager (FTM).

Briefly, I (we) are agreeing that the FTM is crippleware and needs to
include the ability to report the status of the servers it is attempting
to connect to., i.e. a "demand meter" so to speak. Especially during
periods of heavy demand such as the last two weeks when ASP.NET 2.0 was
officially released.

If you guys don't support me on this I will be forced to write my
congressman and ask for the death penalty.

<%= Clinton Gallagher
METROmilwaukee (sm) "A Regional Information Service"
NET csgallagher AT metromilwaukee.com
URL http://metromilwaukee.com/
URL http://clintongallagher.metromilwaukee.com/


[1] http://lab.msdn.microsoft.com/ProductFeedback/Default.aspx
Click to expand...
Click to expand...
Click to expand...
 
Yeah, File Transfer Manager sucks, if you say so.

LOL.

Actually, it just isn't very good, I have to agree.
 
Back
Top