Note: Keep in mind that any speculation on SharePoint 2010 Features at this point is highly speculative. In theory, Microsoft could change the whole thing into a word processor or Minesweeper II – Day of Destruction without anyone being able to complain; don’t base important decisions on pre-release information.
If you have ever worked with developing code on a shared platform, you have likely faced the problem of multiple solutions deployed to the same farm or application.
In SharePoint 2010, Microsoft has gone out of its way to improve the solution framework. I have already written about the SharePoint 2010 Features Upgrade and Versioning support, but apparently, Microsoft has more aces up their sleeves.
Enter the Solution Sandbox. And quite frankly, that’s about all that’s known at this point, but we can deduce something from the newly released SharePoint 2010 SDK beta.
Here’s what I wrote about this in the SharePoint 2010 Beta series of USP Journal, the first issue of which is now free:
“The solution framework is getting a major overhaul, as mentioned, and a class that hints at a new feature here is the SPUserSolution class. The SPUserSolution class allows SharePoint solutions to be deployed at a specific site collection and run in a sandbox on that site without affecting other site collections.
Even more hints at this come from the SPFeatureReceiverProperties class, now exposing a new property called UserCodeSite. The UserCodeSite property returns the site collection object where the current feature runs, or returns null if the feature is globally available.
Sadly, very little other information is available, but an interesting comment may indicate yet another improvement to the framework. The SolutionId property remarks state that multiple solutions in a library may have the same solution ID, and this indicates different versions of the same solution. “
This is a major change in SharePoint, and hopefully, will improve the development experience by allowing isolation of solutions during testing and development. If this is intended as a production scale feature, it will allow shared hosts to deploy solutions only to specific customers. Clearly this would improve the SharePoint hosting experience, and could even be used to allow customers of shared hosts to deploy their own solutions.
But again, this is highly speculative at this point, so ignore everything I just said.
Note: The first issue of the SharePoint 2010 Beta series is now available free, after the major controversy the last couple of weeks where even Microsoft themselves tried to stop this series from being published. However, to get future issues, you will need to sacrifice $14.95 to the well-being of Understanding SharePoint Journal.
Found this article valuable? Want to show your appreciation? Here are some options:
a) Click on the banners anywhere on the site to visit my blog's sponsors. They are all hand-picked and are selected based on providing great products and services to the SharePoint community.
b) Donate Bitcoins! I love Bitcoins, and you can donate if you'd like by clicking the button below.
c) Spread the word! Below, you should find links to sharing this article on your favorite social media sites. I'm an attention junkie, so sharing is caring in my book!