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

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?

share|improve this question

2 Answers 2

up vote 0 down vote accepted

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.

share|improve this answer

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

share|improve this answer

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.
{"cc_re__cc_re__cc_by_sa_3_0": ["        <li><a href=\"http://area51.stackexchange.com\" title=\"proposing new sites in the Stack Exchange network\">Area 51</a></li>\r\n                        <li><a href=\"http://careers.stackoverflow.com\">Stack Overflow Careers</a></li>\r\n                    \r\n                </ol>\r\n            </td>\r\n    </tr>\r\n</table>\r\n                </div>\r\n            </div>\r\n\r\n            <div id=\"copyright\">\r\n                site design / logo &#169; 2014 stack exchange inc; user contributions licensed under <a href=\"http://creativecommons.org/licenses/by-sa/3.0/\" rel=\"license\">cc by-sa 3.0</a> \r\n                with <a href=\"http://blog.stackoverflow.com/2009/06/attribution-required/\" rel=\"license\">attribution required</a>\r\n            </div>\r\n            <div id=\"svnrev\">\r\n                rev 2014.7.25.1726\r\n            </div>\r\n            \r\n        </div>\r\n    </div>\r\n    <noscript>\r\n        <div id=\"noscript-warning\">SharePoint Stack Exchange works best with JavaScript enabled<img src=\"http://pixel.quantserve.com/pixel/p-c1rF4kxgLUzNc.gif\" alt=\"\" class=\"dno\"></div>"], "copyright__copyright__copyright": ["are|improve this answer\n\nIn 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\n\nshare|improve this answer\n\nYour Answer\n\n\u00a0\ndiscard\n\nBy posting your answer, you agree to the privacy policy and terms of service.\n\nNot the answer you're looking for? Browse other questions tagged or ask your own question."]}