•SharePoint foundation 2010 is the replacement of wss.
• SharePoint server 2010 is the replacement of moss.
• In 2010 there is a web part separately for Silverlight.
• Server ribbon in SharePoint 2010 site is developed using Ms-office 2007.
• SharePoint 2010 is using .Net Framework 3.5.
• SharePoint server 2010 will be installed on 64 bit operating system
• The operating systems we can install SharePoint 2010 was Windows server r2 for development or production. We can use windows vista or windows 7 only for development.
• Version of IIS we use was iis7.0.
• Developer dashboard can be enabled using stsadm or power shell.
• Using developer dashboard you can identify which web part is taking how much time to render and you can find issues within your code.
• SharePoint 2007 requires additional configurations to work with Silverlight and Ajax.
• We can create a multiple lookups at one attempt.
• We can restrict a lookup that the user should not delete the item from parent list.
• Lists are rendered using xslt in SharePoint 2010.
• Xslt web part provides a better performance of rendering data.
• Xslt is the default rendering option for SharePoint lists as well as external lists.
• Client object model provides a subset of server object model.
• Visual studio 2010 helps people to retrieve SharePoint lists which are in remote place.
• BCS is used to populate data from external data sources to SharePoint lists which we call as external lists.
• Message apis have been introduced to better understanding of the end user.
• Dialog framework has been introduced for the end user sake to go to next level.
• When you create SharePoint ui to a template it generates as a wsp file.
• We can create a new sitecollection using power shell.
• We can directly open the site within a spd using site actions at the right side of the site.
• We will have all files folder where you can find all files including master pages.
• For a list you create columns using spd.
• You can set the general setting of the site using spd.
• We can create a workflow at the site level.
• Workflow can be seen using Visio services.
• We can reuse spd workflow to visual studio workflow.
• Client object model is of 3 types
• Dotnet.
• Silver Light.
• JavaScript.
• Benefits of Microsoft SharePoint server 2010
• Connect & empower people.
• Cut costs with a unified infrastructure.
• Rapidly respond to business needs.
• SharePoint terminology overview
• First you will have farm.
• After you will have one or more servers.
• Server consists of site collections.
• A site collection consists of various sites.
• Under site collection you will have a TopSite.
• Under TopSite you will have subsite.
• Under subsite you will have one more subsite.
• Under subsite you will have lists or document libraries.
• Under list or documents you will have fields.
• Under fields you will have listitems.
• Improvements with in a workflow.
• Visual studio 2010 initiation and association forms.
• New workflow design surface in spd.
• Import spd workflows into visual studio.
• Build spd actions in visual studio.
• Visio 2010 workflow design.
• Browser based visualization.
• High privilege workflows.
• Control where service runs.
• Site workflows.
• Reusable declarative workflows.
• List workflow event receivers.
• Pluggable workflow services.
• Performance and scale.
• Fully customizable OOB workflow.
• Approval designer.
• Visual studio 2010 developer tools for SharePoint.
• Develop deploy & Debug.
• Web part BCS and workflow designers.
• Package and deploy SharePoint projects.
• SharePoint server 2010 is the replacement of moss.
• In 2010 there is a web part separately for Silverlight.
• Server ribbon in SharePoint 2010 site is developed using Ms-office 2007.
• SharePoint 2010 is using .Net Framework 3.5.
• SharePoint server 2010 will be installed on 64 bit operating system
• The operating systems we can install SharePoint 2010 was Windows server r2 for development or production. We can use windows vista or windows 7 only for development.
• Version of IIS we use was iis7.0.
• Developer dashboard can be enabled using stsadm or power shell.
• Using developer dashboard you can identify which web part is taking how much time to render and you can find issues within your code.
• SharePoint 2007 requires additional configurations to work with Silverlight and Ajax.
• We can create a multiple lookups at one attempt.
• We can restrict a lookup that the user should not delete the item from parent list.
• Lists are rendered using xslt in SharePoint 2010.
• Xslt web part provides a better performance of rendering data.
• Xslt is the default rendering option for SharePoint lists as well as external lists.
• Client object model provides a subset of server object model.
• Visual studio 2010 helps people to retrieve SharePoint lists which are in remote place.
• BCS is used to populate data from external data sources to SharePoint lists which we call as external lists.
• Message apis have been introduced to better understanding of the end user.
• Dialog framework has been introduced for the end user sake to go to next level.
• When you create SharePoint ui to a template it generates as a wsp file.
• We can create a new sitecollection using power shell.
• We can directly open the site within a spd using site actions at the right side of the site.
• We will have all files folder where you can find all files including master pages.
• For a list you create columns using spd.
• You can set the general setting of the site using spd.
• We can create a workflow at the site level.
• Workflow can be seen using Visio services.
• We can reuse spd workflow to visual studio workflow.
• Client object model is of 3 types
• Dotnet.
• Silver Light.
• JavaScript.
• Benefits of Microsoft SharePoint server 2010
• Connect & empower people.
• Cut costs with a unified infrastructure.
• Rapidly respond to business needs.
• SharePoint terminology overview
• First you will have farm.
• After you will have one or more servers.
• Server consists of site collections.
• A site collection consists of various sites.
• Under site collection you will have a TopSite.
• Under TopSite you will have subsite.
• Under subsite you will have one more subsite.
• Under subsite you will have lists or document libraries.
• Under list or documents you will have fields.
• Under fields you will have listitems.
• Improvements with in a workflow.
• Visual studio 2010 initiation and association forms.
• New workflow design surface in spd.
• Import spd workflows into visual studio.
• Build spd actions in visual studio.
• Visio 2010 workflow design.
• Browser based visualization.
• High privilege workflows.
• Control where service runs.
• Site workflows.
• Reusable declarative workflows.
• List workflow event receivers.
• Pluggable workflow services.
• Performance and scale.
• Fully customizable OOB workflow.
• Approval designer.
• Visual studio 2010 developer tools for SharePoint.
• Develop deploy & Debug.
• Web part BCS and workflow designers.
• Package and deploy SharePoint projects.
No comments:
Post a Comment