550 error - what does VS FTP deploy do differently than a standard ftp client?

Question

User-1463593185 posted

I have a website on DailyRazor that, with a standard FTP client, I can upload files just fine to. All permissions are correct. However, when I try to publish via Visual Studio, I get 550 errors:

Unable to add 'favicon.ico' to the Web site. Access is denied (550).
Unable to add 'Global.asax' to the Web site. Access is denied (550).
Unable to add 'packages.config' to the Web site. Access is denied (550).
Unable to add 'Web.config' to the Web site. Access is denied (550).
Unable to add folder 'bin' to the Web site. Cannot create folder "bin".
Unable to add folder 'Content' to the Web site. Cannot create folder "Content".
Unable to add folder 'Images' to the Web site. Cannot create folder "Images".
Unable to add folder 'Scripts' to the Web site. Cannot create folder "Scripts".
Unable to add folder 'Views' to the Web site. Cannot create folder "Views".

Does anyone know what VS may be doing differently than my other FTP clients that would cause this? 

Answer 1

User-1463593185 posted

Never mind, the difference was that VS was pointing to the wrong directory. Whoops 

Answer 2

User-166373564 posted

Hi ddeutsch

the difference was that VS was pointing to the wrong directory.

Thanks for your kind feedback, and I come here to confirm and close the issue. If you have anything urgent, please feedback by creating another issue.

With regards