Imp Notes SharePoint 2010
While working with SharePoint Linq Concept Linq converts the query written into caml query language which was understood by SharePoint.
Asset Library:-
A place to share, Browse and manage rich media assets like image, audio & video files.
Translation Management Library:-
This library was useful when u want to create documents in multiple languages and manage translation tasks. Translation management libraries include a workflow to manage the translation process and provide sub-folders, file versioning and checkin & Checkout.
External List:-
Allows you to display external data in this list.
Ex: - Sql Server, sap etc.
Note:-
You can Read & write also. It will be reflected into the external list.
Languages and Translators:-
Creates a list of languages for which the translation management workflow will assign translation tasks. You can also specify the translators for each language.
Business Connectivity Services:-
Business Connectivity Services is the new version of Business Data Catalog in SharePoint 2007.
In SharePoint 2010 There are read as was well as write capabilities.
Silverlight Integration:-
In SharePoint2007 it’s very difficult to integrate with Silverlight concepts. But here in 2010 was introduced a Silverlight object model which works with client object model in SharePoint 2010.
While working with SharePoint Linq Concept Linq converts the query written into caml query language which was understood by SharePoint.
Asset Library:-
A place to share, Browse and manage rich media assets like image, audio & video files.
Translation Management Library:-
This library was useful when u want to create documents in multiple languages and manage translation tasks. Translation management libraries include a workflow to manage the translation process and provide sub-folders, file versioning and checkin & Checkout.
External List:-
Allows you to display external data in this list.
Ex: - Sql Server, sap etc.
Note:-
You can Read & write also. It will be reflected into the external list.
Languages and Translators:-
Creates a list of languages for which the translation management workflow will assign translation tasks. You can also specify the translators for each language.
Business Connectivity Services:-
Business Connectivity Services is the new version of Business Data Catalog in SharePoint 2007.
In SharePoint 2010 There are read as was well as write capabilities.
Silverlight Integration:-
In SharePoint2007 it’s very difficult to integrate with Silverlight concepts. But here in 2010 was introduced a Silverlight object model which works with client object model in SharePoint 2010.
Client object Model:-
Client object model allows users to interactively connect with Silverlight which works with in a client. Instead of working with Webservices Client object Model helps you to connect from SharePoint list to Silverlight which we are calling it as Silverlight object model also.
Note:-
You can use Client Object Model within a WebPart also.
Integration with Ajax:-
In SharePoint 2007 it’s difficult to integrate with Ajax. Now in SharePoint 2010 by default the site was integrated with Ajax. In 2007 you have to go to web.config & do some operations to integrate with Ajax. And even for visual studio you have to install a separate template. Due to all this processes it will be a burden to the server. SharePoint 2010 made it so easy to integrate with Ajax.
Sandbox Solutions:-
Suppose if a developer needs to deploy their WebPart in SharePoint2007 he should have an Administrator privileges to deploy their Webparts. Administrator will not allow the developers to deploy their WebPart with elevated privileges to deploy it as a solution. This problem was solved in SharePoint 2010. Microsoft Introduced a new concept called sandbox solutions. Even though developer is having non admin privileges he can deploy his WebPart using Sandbox solutions. One of the advantages of using this was the webparts deployed will be under the control of Administrator. After the approval of admin only this will be populated to the respective site. Sandbox solutions will run under other process. Suppose if you are having a problem with WebPart published with sandbox solutions only that WebPart will have the problem. Other work will not get disturbed. Even Admin can identify which WebPart was causing the problem & he can remove that WebPart from the particular site.
Client object model allows users to interactively connect with Silverlight which works with in a client. Instead of working with Webservices Client object Model helps you to connect from SharePoint list to Silverlight which we are calling it as Silverlight object model also.
Note:-
You can use Client Object Model within a WebPart also.
Integration with Ajax:-
In SharePoint 2007 it’s difficult to integrate with Ajax. Now in SharePoint 2010 by default the site was integrated with Ajax. In 2007 you have to go to web.config & do some operations to integrate with Ajax. And even for visual studio you have to install a separate template. Due to all this processes it will be a burden to the server. SharePoint 2010 made it so easy to integrate with Ajax.
Sandbox Solutions:-
Suppose if a developer needs to deploy their WebPart in SharePoint2007 he should have an Administrator privileges to deploy their Webparts. Administrator will not allow the developers to deploy their WebPart with elevated privileges to deploy it as a solution. This problem was solved in SharePoint 2010. Microsoft Introduced a new concept called sandbox solutions. Even though developer is having non admin privileges he can deploy his WebPart using Sandbox solutions. One of the advantages of using this was the webparts deployed will be under the control of Administrator. After the approval of admin only this will be populated to the respective site. Sandbox solutions will run under other process. Suppose if you are having a problem with WebPart published with sandbox solutions only that WebPart will have the problem. Other work will not get disturbed. Even Admin can identify which WebPart was causing the problem & he can remove that WebPart from the particular site.
Access & Visio Services:-
Access Services will allow customers to publish their Access 2010 applications to SharePoint. For example, consider a departmental application such as a travel planner built using Access. Using Access Services it will be possible to bring such an application to SharePoint, thereby reducing the total cost of ownership through one common user experience, development and deployment strategy.
Similarly, Visio Services will allow customers to render Visio diagrams within the browser. An application of Visio Services would be a visualization of a SharePoint workflow that is rendered inside a browser as a Visio flowchart. Note that no client-side Visio software would be needed in this scenario.
Developer Dashboard:-
This tool allows the developer to know exactly which WebPart was taking how much time & can identify where the problem is there within his code. This was a new tool which was not available in SharePoint 2007. This tool was helpful to increase the performance of your SharePoint site.
No comments:
Post a Comment