Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

Is there a way to use FTP with SharePoint?

I'd like to build a project, then just upload it to a directory that is set to automatically publish anything that is uploaded to the directory. In other words, a way to use SharePoint as a basic web host, not a complex CMS. If I could upload via FTP and see it online without having to login to SharePoint at all, this would be most ideal for this use-case.

EDIT

I didn't choose to install SharePoint, but we have migration of old microsites and other content which need to be hosted on our SharePoint install.

share|improve this question
3  
Use "SharePoint as a basic web host, not a complex cms" - why don't use use a basic web host then? Whats your reasoning here? Why use a sledgehammer for a nut? –  Ryan Jun 23 '11 at 22:58
    
The installation of SharePoint on a server doesn't disable regular IIS use. If you are familiar with IIS, you can create another website on the same server that doesn't use SharePoint and use it as you normally would. The only issue I could see with that is having multiple web site addresses, but maybe that's not an issue for you. –  Tom Resing Jun 26 '11 at 0:34
add comment

5 Answers

I agree with Ryan. If you just want to ftp files up to a server, well just ftp files to your IIS virtual directory. If that is all you want to do, why install SharePoint? Of course, you'll presumably have to log in to your ftp server, so maybe it isn't that much simpler.

If you want a back-to-basics approach you could try using SharePoint to provision your site and use WebDAV to drop files onto Windows Explorer. Or you could use SharePoint Designer as a tool to edit and upload simple pages. There are many possibilities and you certainly don't need to go for the all-out SharePoint Publishing model. But if you want to keep things as simple as possible then why use SharePoint at all?

share|improve this answer
    
See edit above.. –  Kirk Strobeck Jun 23 '11 at 23:54
2  
I have used this type of approach to bring an ASP.NET site under the SharePoint umbrella - the main challenge being if you have code-behind, which has to be modified. Static pages and assets are relatively easy. –  SPDoctor Jun 24 '11 at 7:45
add comment

FTP is not one of the supported protocols.

SharePoint isn't really configured to upload "external" sites and host them. Utilizing IIS as state above is more appropriate. If you don't have access at that level, your best bet is planning a true migration. There are tools available from AvePoint, Quest, and others to assist with migrating traditional websites into SharePoint.

http://www.metalogix.com/products/migration-manager-for-sharepoint/SharePoint-Upgrade.aspx

http://www.quest.com/sharepoint/migration.aspx

http://www.avepoint.com/sharepoint-migration-tools/

share|improve this answer
    
Can you please expand on these tools? What's best for this use-case? –  Kirk Strobeck Jun 24 '11 at 2:46
    
What's best depends on your case. Evaluate every tool and choose the best one which suits your need. –  Shoban Jun 24 '11 at 4:23
    
I've added links to the big 3 vendors, there are of course more, and just like @Shoban stated, you need to evaluate each one and see if they will meet your needs. No migration tool is trouble free, and there will be work to do once your content is moved. –  Jesus Shelby Jun 24 '11 at 12:38
add comment

It seems to me that you are wanting the tool to meet some perceived technical need instead of defining the need and arriving at the right tool. Even if there are some forcing functions which are causing you to feel you must use SharePoint, it may be the wrong answer.

On the flip side, if you think through the details of what you want to accomplish from a business, not technical, perspective, then SharePoint may provide you much better options than FTP. If you want to organize, categorize, and index the content in a more E2.0 fashion, then SharePoint may be exactly the sledgehammer you need.

share|improve this answer
    
See edit above.. –  Kirk Strobeck Jun 27 '11 at 17:19
    
The edit was there when I replied, and I saw it. My answer stands! –  Marc D Anderson Jun 27 '11 at 17:46
add comment

We had a related question recently here

In general it is considered a bad practice to use SharePoint as a file share. The same goes, I guess (unless you have a business case to prove otherwize) for SharePoint as an FTP host...

share|improve this answer
    
See edit above.. –  Kirk Strobeck Jun 23 '11 at 23:54
add comment

The good way reliably upload large files to Sharepoint is to use the FrontPage Remote Control Procedures, these requires you install the FrontPage extension component on your Sharepoint server but allow you to bypass the Windows based 2MB limit, as it must normally allocate in continuous memory.

The RPC calls are commonly used in Office applications.

All though it's not the best documented method by Microsoft, this blog article explains the process pretty well. I also found this code snippet that contains an example of an helper class which will allow you to upload in this method. I found this was enough to get a functioning test project and adapt it to my needs!

In regards to "Don't use Sharepoint for file sharing", I my experience many people are pitched Sharepoint for inappropriate tasks. It bundles a lot of features so people like to do "Oh we can use Sharepoint for this to!" style thinking.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.