Sandbox Solution + Sharepoint 2010

Sandboxing solutions


Sandboxed Solutions is a new concept in Sharepoint 2010 . It helps you to run your custom code in a highly isolated environment. Initially in MOSS 2007 the custom code had to be deployed to central admin which used to be deployed to the site and then was available for the end user to use.

But now with Sharepoint 2010 the user can write custom code and upload it in the solution gallery of the site and its available for use.

Use of Sandbox solution
1. It reduces the time to deploy custom solutions
2. Improves stability of the sharepoint server
3. Any worst written code will not bring down the sharepoint farm (it helps code to be run in partially trusted environment)
4. Custom solution can be uploaded in solution gallery and can be activated as sandboxed solution.
5. SPsite and objects below it are supported in the sandboxed solutions
6. It restricts the intellisense as it runs code in highly isolated environment
  (If you copy paste an external code in sandbox solution it will run and compile solution as sandbox but will give error at run time)
eg: SPSecurity. Runwithelivated privelages is not allowed in sandbox solution but if u paste the code in case of webparts it will allow to run the code but will show error when webpart is added to page.The advantage of using sandboxed solution is that even if there is error in the webpart page, entire page will be loaded with error in webpart. As in 2007 if there was error in page the page would not be rendered

Allow execution

SPUCHost service.exe should be started on each farm to allow the use of sandboxed solution
This in turn starts SPUC workerprocess.exe
and SPUCworkerprocessProxy.exe

Define Sandboxing  
1. Solution Administration
2. Subset of object model
3. External process
4. Code Access Security policies(CAS)

Sharepoint 2010 Managed Metadata Services

Sharepoint 2010 has a new service called the Managed Metadata Service . It was not avilable in the previous versions of Sharepoint.

In the SSP's what the problem was we dint have the option to pick and choose services . All services that were within the SSP had to be utilized , but now with the new service architecture in 2010 we adopt the
Service "al a carte " Model which allows us to pick and choose services across the farm.

Now in SP 2010 whenever we create a new web application we have the option of choosing from a list of services we want to use within our web-appilication .

Now with managed metadata service what option we have is we can now use the content type and the metadata available in one site collection across all site collections
1. In managed metadata service application we can add the "HUB" - one site collection name
    and many other site collections can act as a subscriber.
2. Suppose we create a content type within the HUB site collection we can use it across all site collections in 
    the farm , which was not possible in SP 2007. If we had to use the existing content type of one site
    collection it had to be exported and the imported back to site collection. But now with managed metadata
    services we can do that easily.

1. When we create a new Managed Metadata Service we get two links according to name given.
   Suppose you name it "GlobalManagedMetadata" . Then it creates two links
   i GlobalManagedMetadata
   ii GlobalManagedMetadata Connections

Global Managed metadata takes us to the term store Management tool where we can create new groups, termsets and terms.
Structure is groups> can have termsets> terms are within termset
This can be used as site columns for ur content type.

In connection settings you need to check pick the content from the HUB site.

Another important thing is you need to do is after creating content type you need to  publish the content type and then restart the timer job services for you to use the content types across the site collection. (Its available im monitoring section of central admin)

Logical Architecture Sharepoint 2010

Logical Architecture Sharepoint 2010

v Logical Architecture is definition of how your portal is built, including the

    hardware, software service and other integrated components

v It includes the following services and features of SharePoint

v New Metadata Services

v Extensive Social features

v Multi user office support

v Search improvements

v Large repository

v Digital Asset Support

 

Logical Architecture Changes in Sharepoint 2010

 

v  Moved away from SSP Model and adopted “a la carte” model

 

Ø  This model allows u to pick and choose services you want to use  within SharePoint Farm

Ø  In SP 2007 we had finite set of services and every web application in the farm that used that SSP had to   consume each and every service of the SSP

Ø   In Sp 2010 we breakout the services and allow you to choose services  within web applications

v  Improvement in Application Integration

 

Ø  It allows you to create custom services application and use it in Sharepoint Farm

v  Large Lists Improvements

 

Ø  Allows list and libraries to be much larger than in SP 2007. Recommended

     not to exceed 30,000,000 docs per document library/list.

 

 v  Multi user office support

      upto 10 users can edit or modify the same document. The changes reflect  when you save the  document. If you are using office web app then changes  reflect in the browser itself.

 

 vDigital Asset feature: Video :Silverlight media player webpart and video content type: to view thumbnails, images, copyright information. Same is applicable for audio and images content types

 

vExtensive Social features : It allows us to create upto 2 million user profiles with full social networking  features. It also allows user to personalize sites using the Mysite feature.

if you want to read about Sharepoint foundation 2010 : click here

Installation Problem 2009

Hi
i installed BizTalk 2009 , it was installed successfully .
Now i am facing one problem .
when i opened visual studio 2008 in template list BizTalk is not showing
can any one help me out of this issue ?

Thanks,
kotireddy B