very slow FTP

Question

_{Friday, December 14, 2007 11:14 AM}

Hi All: I usually connect to websites that have FPSE installed, and VWD works fine with this connection, but if I try to use FTP to connect to a website, opening and saving files is painfully slow. Using a simple FTP client like SmartFTP or even running FTP from the command line is much faster. Is there a setting or something I can do in VWD to make it work faster with FTP?

All replies (7)

_{Monday, September 28, 2009 2:13 PM ✅Answered}

Just some final observations:

• VWD2008Express sp1 did not resolve the slow ftp.
• FTP performance when connecting to Server 2008 was much better than Server 2003 (?).
• Upgrading from Vista sp2 to Windows 7 RTM resolved all the FTP issues. FTP just flies on Windows 7...yay

_{Friday, December 14, 2007 11:24 AM}

It is slow, mostly because it does a crummy job of caching files it's already downloaded. I would recommend not using FTP if performance is a big thing, rather I would setup your application on your local development machine, work with it from there, then upload your changes once it's working properly. This feature has been around since VS 2005, and there was no change in performance (That I noticed) since then.

_{Friday, December 14, 2007 11:24 AM}

Just commenting on my own post...I've read threads here over the past year about slow FTP in VWD, and I understand why it would take a long time to open a remote website, but even after it's been cached locally, opening and saving small (<10K) files is painfully slow.

For Server2008, is there any other way of publishing, short of installing FPSE, which is not supported by Microsoft? Are people installing Sharepoint services or something else, or are they just using FTP?

_{Monday, April 28, 2008 7:51 PM}

Hi,

As a part of creating a way for customers to directly communicate with the product team and get help if they are running into performance issues in Visual Web Developer 2008 or web-related features in Visual Studio 2008, the product team has created a public alias to report all performance related concerns about the product. The alias is vwdperf-at-microsoft-dot-com. Can you please contact this alias with your performance issues? All emails to this alias will be looked into and duly responded to.

-Ranjini

_{Wednesday, June 11, 2008 10:25 AM}

I've sent several emails to the address above, and none was "duly responded to" or even acknowledged...has anyone else gotten a response? Is the subject dead at this point?

I'm just wondering if the problems I've been having (and continue to have) are isolated or if other people are experiencing them as well?  Maybe it's my firewall in front of the servers or something else on my network, but I can't seem to get decent connection speeds with FTP or FPSE no matter which server I'm connecting to  (win2k, 2003R2 or 2008).[:'(]

_{Friday, October 2, 2009 6:47 AM}

cool, I must try

probably at the end of October

_{Friday, October 2, 2009 2:06 PM}

I have the same problem with my VWD2008 Express, and I have updated the system. I can login using FTP with the VWD2008, but I can't list the remote directory.

The web server only use actives connection, and I can use FTP via MS-DOS shell normally, it work's perfect if I list or change files on the remote directory.

I'm using a Windows XP with SP3 applied, and I uninstall the firewall in my box.

If I use VWD2005 Express in other computer, I can download and change my files on the remote web server normally. I suspect that the problem is the FTP client of VWD2008, it may be only works in passive mode and I've uncheck the passive option from my IE 7.

I can look the network connections using MS-DOS shell, I can look that the 21/TCP port is established, but when list the directory, the networks connection try list files using high remote port on the web server. May be that ftp client VWD2008 works only forced using passive mode.

Ideas how fix? Thanks