Over the past couple of years I've been making solutions for SharePoint Server and always most important problem was the availability of the web-site. Deployment not-sandboxed solution is pain at least for 30 seconds for each wsp. This operation requires recycle of Application Pool (include the farm one) and in fact this means 503 Service Unavailable http response from IIS Server.

We usaully use SharePoint for external Internet web sites and we expect the highest possible percentage of availability. (Two farm for replication, powershell-automation, read-only mode while deploying, etc.)

Yesterday Microsoft released SharePoint 13 Preview. I've just downloaded slides1 and see there

Never any reason to have separate farms (Except security)

Any possibility for another deploy scheme?

2 Answers 2


I believe the statement is more related to Office Web Apps capabilities rather than overall SharePoint farm or deployed solutions. In your case, probably you should consider using more Sandboxed solutions, or re-architect farm solutions to include part of these as sandboxed solutions, because the trend set out for the future is cloud compatibility, etc., which starts with you not really having the possibility to deploy farm solutions.

The reason why SP2013 now has a "Store" built-in which deploys sandboxed solutions only.

  • Sounds reasonable, thanks. Alse, for difficult application we start using ASP.NET MVC integrated through SharePoint REST API and Custom Web Services. Jul 19, 2012 at 1:58

In SharePoint 2013 the general direction is away from any code on the server. They've enhanced client site object mode/REST as well as created the new posibility for Apps where you run the code outside SharePoint, but get permissions though OAuth tokens


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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