Visual Studio 2010 Publishing So Slow

Question

I'm using Visual Studio 2010 Premium, and find publishing via FTP through Visual Studio's build in publishing mechanism to be painfully slow. If I choose to manually FTP (with a client like FileZilla), I'm able to publish much quicker. Although I haven't measured it, publishing the whole site (i.e. overwriting all files) with FileZilla is in the neighborhood of 10 times faster than the incremental publishing of Visual Studio. Is anyone else experiencing this? Is there a way to address this issue?

Thanks

Marisolmarissa

I'm experiencing this as well. I'm watching the incoming request in FileZilla Server, and it is really slow. Recreating requests, re-entering PASV mode, etc. It really sucks. – Diego

Answer 1

scenario: you don't mind publishing your source code, and you need to publish via ftp. visual studio's built in "copy web site" tool is prohibitively slow because it scans the server for changes and your website has many folders and files, but analyzing the server is unnecessary because you are the only person who updates your website.

solution: "web site publisher", the simplest and most genius program ever. it took me many hours to find it, which is why i felt the need to share it. you can configure it to scan only your hard drive for new/changed files and deletions, and then publish the changes since you last published to the ftp server. my solution won't work for pre-compiled asp.net web applications; works well for regular asp.net web sites.

download it here: http://www.cryer.co.uk/downloads/websitepublisher/

you must enable the turbo optimization so that it does not scan the server. click "config", "optimisations", and then check "turbo".

here's my blog post saying the exact same thing: http://devblog.alexsapps.com/2012/04/visual-studio-2010-copy-web-site-tool.html

Averir

shame it does not support precompiled sites :( – Himmler