Microsoft always provide us better environment and great platform to perform our task,so moving ahead in this Microsoft provide SharePoint for developing website,portals,content management system etc.now i'm going to describ briefly what is Sharepoint, history of SharePoint.
What is SharePoint ?
Microsoft SharePoint, is a software platform and a family of software products developed by Microsoft for collaboration and web publishing combined. These capabilities include developing web sites, portals, intranets, content management systems, search engines, wikis, blogs, and other tools for business intelligence. This family of products include: Microsoft SharePoint Server, Microsoft SharePoint Foundation, Microsoft Search Server, Microsoft SharePoint Designer and Microsoft SharePoint Workspace.
History of SharePoint
The first version, called SharePoint Team Services (usually abbreviated to STS), was released at the same time as Office XP and was available as part of Microsoft FrontPage. STS could run on Windows 2000 Server or Windows XP.
Windows SharePoint Services 2.0 was marketed as an upgrade to SharePoint Team Services, but was in fact a completely redesigned application. SharePoint Team Services stored documents in ordinary file storage, keeping document metadata in a database. Windows SharePoint Services 2.0 on the other hand, stores both the document and the metadata in a database, and supports basic document versioning for items in Document Libraries. Service Pack 2 for WSS added support for SQL Server 2005 and the use of the .NET Framework 2.0.
Windows SharePoint Services 3.0 was released on November 16, 2006 as part of the Microsoft Office 2007 suite and Windows Server 2003. WSS 3.0 is built using .NET Framework 2.0 and .NET Framework 3.0 Windows Workflow Foundation to add workflow capabilities to the basic suite. By the beginning of 2007 WSS 3.0 was made available to the public. Windows 2000 Server is not supported by WSS 3.0.
WSS version 3 marked a significant maturation of the product. Version 3 supported more features commonly used in Web 2.0 solutions like Blogs, Wikis and RSS feeds. Microsoft has launch next version 4.0 to SharePoint Foundation 2010.
Features in SharePoint Foundation 2010
Microsoft SharePoint Foundation (formerly known as Windows SharePoint Services) is a free add-on to Microsoft Windows Server 2003 and 2008 providing a web portal with commonly needed features.
1. Alerts Enhancements
Microsoft SharePoint Foundation 2010 expands the alerts framework to enable users to have alerts sent as Short Message Service (SMS) messages to their mobile devices.
Extensible Mobile Messaging Framework
________________________________________
SharePoint Foundation 2010 takes advantage of the new mobile messaging framework to enhance its Alerts feature. To support the new option, the SPAlert class now has a property that indicates whether the alert is delivered as e-mail or as an SMS message. The SharePoint Foundation Web application is given its own account, which can be programmatically changed, with a mobile messaging service provider.
The mobile messaging framework is itself extensible, so you can create your SharePoint Foundation solutions that incorporate SMS messages that are sent to mobile telephones. You can create a completely customized alert system if you want. If your messaging solution uses the Office Mobile Service (OMS) protocol, most of your development work has already been done for you. A rich set of classes has been added to the object model to represent the Web Methods and response types of the protocol. If your solution requires a different protocol, base classes have been provided with default implementations of essential properties and methods.
2. Business Connectivity Services
Microsoft Business Connectivity Services (BCS), formerly named the Business Data Catalog, provides read/write access to external data from line-of-business (LOB) systems, Web services, databases, and other external systems within Microsoft SharePoint 2010. SharePoint 2010 has product features that can use external data directly, both online and offline. Developers can gain access to a rich set of features and rapidly build solutions by using familiar tools such as Microsoft Visual Studio 2010 and Microsoft SharePoint Designer 2010.
Business Connectivity Services enhances SharePoint application capabilities and their UI through features, services, and tools. These enhanced capabilities and UI streamline development of solutions with deep integration of external data and services. Power users, developers, and business unit IT professionals can integrate assets from external systems and enable interaction with the external data through many types of applications. The Business Connectivity Services feature set enables rapid development and deployment of scalable and security-rich solutions.
The following are some of the features of Business Connectivity Services.
Write-back to External Systems
________________________________________
Using Business Connectivity Services, you can create, read, update, delete, and query (CRUDQ) to the external system from a Microsoft Office application or SharePoint site if the external system supports the operations and is modeled appropriately in the Business Data Connectivity (BDC) service.
Familiar UI
________________________________________
External content types provide SharePoint behaviors (such as lists, Web Parts, and profile pages) to external data and services. As a result, users can work in their familiar work environments without needing to learn different (and often proprietary) user interfaces.
More Connectivity Options
________________________________________
The core function of BDC is to provide connectivity support to the following types of external systems:
• Databases
• Web and Windows Communication Foundation (WCF) services
• Microsoft .NET connectivity assemblies
• Custom data sources
Extensible Provider Model
________________________________________
In addition to connectors for the previous list of data sources provided by BDC, BDC provides a pluggable framework with which developers can plug in connectors for new external system types, thus enabling these new data source types to be accessed via the BDC.
Batch and Bulk Operation Support
________________________________________
In Office SharePoint Server 2007, BDC supported only single item operations, such as search. BDC now provides batch and bulk operation support which enable you to read multiple items in a single call thus reducing round trips to the backend dramatically.
Read BLOBs
________________________________________
BDC now supports reading Binary Large Object (BLOB) data. This is useful for streaming BLOBs of data from the external system.
Read and Write-back of Complex Types
________________________________________
BDC now supports dot notation in field names and therefore enables you to read and write complex types.
Life Cycle Management
________________________________________
Business Connectivity Services provides a set of tools to facilitate creation of models and Office 2010 application artifacts, declaratively and by writing code. You can use SharePoint Designer 2010 to rapidly create composite solutions that meet external unit needs without writing code. You can use Visual Studio to create or extend solutions with sophisticated workflows and data that spans structured LOB systems, unstructured SharePoint applications or Microsoft Office applications, and Web 2.0 services.
Enhanced API Set and Extensibility
________________________________________
Developers can use the BDC Runtime object model to write generic applications by using the stereotyped APIs as building blocks. Such generic applications are then assured to work against any external system, including those that are preexisting and those that are yet to be built.
Developers can also write specific applications that make assumptions about the abstract entity model (the fields exposed by these, and the types of the fields).
And with the .NET Assembly Connector, Custom Connector and the pluggable Secure Store Provider, it provides a rich extensibility mechanism for software developers.
3. Client Object Model
________________________________________Microsoft SharePoint Foundation 2010 introduces three new client APIs for interacting with SharePoint sites: from a .NET managed application (not earlier than Microsoft .NET Framework 3.5), from a Microsoft Silverlight application (not earlier than Silverlight 2.0), or from ECMAScript (JavaScript, JScript) that executes in the browser. These new APIs provide access to a subset of the types and members that are contained in the Microsoft.SharePoint namespace of the server-side object model.
The new client object models provide an object-oriented system for interoperating with SharePoint data from a remote computer, and they are in many respects easier to use than the already existing SharePoint Foundation Web services. You start by retrieving a client context object that represents the current request context, and through this context, you can obtain access to client objects at site-collection level or lower in the SharePoint Foundation hierarchy. Client objects inherit from the ClientObject class (ECMAScript: ClientObject), and you can use them to retrieve properties for a specific SharePoint object, to retrieve child objects and their properties, or to retrieve child items from a collection.
4 Custom Field Rendering Enhancements
Microsoft SharePoint Foundation 2010 makes two significant changes to the way that you define how custom field types render.
XSLT Stylesheet Rendering on List Views
________________________________________
In Windows SharePoint Services 3.0, fields were rendered on list view pages by a RenderPattern element in a field definition file, fldtypes*.xml. In SharePoint Foundation 2010, fields are rendered on list view pages by XSLT stylesheets. Consequently, you now define the rendering of your custom field types by creating a custom XSLT stylesheet rather than adding a custom RenderPattern element to a field type definition. See How to: Create a Custom Field Type Definition and Understanding the FldTypes.xml File for more information about field type definitions. See Overview of XSLT List View Rendering System and How to: Customize the Rendering of a Field on a List View for more information about XSLT rendering and how to customize it.
RenderPattern Elements are Now Obsolete
________________________________________
In Windows SharePoint Services 3.0, fields were also typically rendered in Display mode by means of a RenderPattern element in a field definition file. It was also possible, although rare, to render a field in Edit and New modes with a RenderPattern element. It was more common to render fields in Edit and New modes with a user control (ASCX), known as a RenderingTemplate, and it was possible to use a user control to render a field in Display mode. In SharePoint Foundation 2010, custom fields should always be rendered with user controls in all three modes. Although some long-standing built-in fields still use a RenderPattern element, for development of custom fields RenderPattern elements are obsolete.
PropertySchema Elements are Now Obsolete
________________________________________
In Windows SharePoint Services 3.0, when a custom field had a variable property (that is, a property with a different value on different lists), a control was needed on the New Site Column, Change Site Column, Create Column, and Change Column pages so that users could set the property value. One of the ways that custom field designers could define the rendering of this control was with a PropertySchema element in a field definition file. This method is now obsolete. You should create an editing control as a user control (ASCX). Point your custom field to the user control by setting the FieldEditorUserControl property. For more information about such editor controls, see Custom Field Type Property Rendering and How to: Create an Editor Control for a Field Type Property.
Backward Compatibility
________________________________________
If there is no user control (RenderingTemplate) for a field, the runtime looks for a RenderPattern element in the field type definition file and, if found, uses it. One implication of this behavior is that custom fields that you created for versions earlier than SharePoint Foundation 2010 can still use their existing field type definitions with RenderPattern elements for Display, Edit, or New mode.
SharePoint Foundation 2010 will not automatically render your legacy custom fields on list views by using the Render Pattern in the field type definition for the field. However, if you do not want the default rendering that is given to the field by the XSLT stylesheet, you can re-enable the RenderPattern by adding aTRUE element to the field type definition. For more information, see Understanding the FldTypes.xml File and RenderPattern Element (Field Types).
What is SharePoint ?
Microsoft SharePoint, is a software platform and a family of software products developed by Microsoft for collaboration and web publishing combined. These capabilities include developing web sites, portals, intranets, content management systems, search engines, wikis, blogs, and other tools for business intelligence. This family of products include: Microsoft SharePoint Server, Microsoft SharePoint Foundation, Microsoft Search Server, Microsoft SharePoint Designer and Microsoft SharePoint Workspace.
History of SharePoint
The first version, called SharePoint Team Services (usually abbreviated to STS), was released at the same time as Office XP and was available as part of Microsoft FrontPage. STS could run on Windows 2000 Server or Windows XP.
Windows SharePoint Services 2.0 was marketed as an upgrade to SharePoint Team Services, but was in fact a completely redesigned application. SharePoint Team Services stored documents in ordinary file storage, keeping document metadata in a database. Windows SharePoint Services 2.0 on the other hand, stores both the document and the metadata in a database, and supports basic document versioning for items in Document Libraries. Service Pack 2 for WSS added support for SQL Server 2005 and the use of the .NET Framework 2.0.
Windows SharePoint Services 3.0 was released on November 16, 2006 as part of the Microsoft Office 2007 suite and Windows Server 2003. WSS 3.0 is built using .NET Framework 2.0 and .NET Framework 3.0 Windows Workflow Foundation to add workflow capabilities to the basic suite. By the beginning of 2007 WSS 3.0 was made available to the public. Windows 2000 Server is not supported by WSS 3.0.
WSS version 3 marked a significant maturation of the product. Version 3 supported more features commonly used in Web 2.0 solutions like Blogs, Wikis and RSS feeds. Microsoft has launch next version 4.0 to SharePoint Foundation 2010.
Features in SharePoint Foundation 2010
Microsoft SharePoint Foundation (formerly known as Windows SharePoint Services) is a free add-on to Microsoft Windows Server 2003 and 2008 providing a web portal with commonly needed features.
1. Alerts Enhancements
Microsoft SharePoint Foundation 2010 expands the alerts framework to enable users to have alerts sent as Short Message Service (SMS) messages to their mobile devices.
Extensible Mobile Messaging Framework
________________________________________
SharePoint Foundation 2010 takes advantage of the new mobile messaging framework to enhance its Alerts feature. To support the new option, the SPAlert class now has a property that indicates whether the alert is delivered as e-mail or as an SMS message. The SharePoint Foundation Web application is given its own account, which can be programmatically changed, with a mobile messaging service provider.
The mobile messaging framework is itself extensible, so you can create your SharePoint Foundation solutions that incorporate SMS messages that are sent to mobile telephones. You can create a completely customized alert system if you want. If your messaging solution uses the Office Mobile Service (OMS) protocol, most of your development work has already been done for you. A rich set of classes has been added to the object model to represent the Web Methods and response types of the protocol. If your solution requires a different protocol, base classes have been provided with default implementations of essential properties and methods.
2. Business Connectivity Services
Microsoft Business Connectivity Services (BCS), formerly named the Business Data Catalog, provides read/write access to external data from line-of-business (LOB) systems, Web services, databases, and other external systems within Microsoft SharePoint 2010. SharePoint 2010 has product features that can use external data directly, both online and offline. Developers can gain access to a rich set of features and rapidly build solutions by using familiar tools such as Microsoft Visual Studio 2010 and Microsoft SharePoint Designer 2010.
Business Connectivity Services enhances SharePoint application capabilities and their UI through features, services, and tools. These enhanced capabilities and UI streamline development of solutions with deep integration of external data and services. Power users, developers, and business unit IT professionals can integrate assets from external systems and enable interaction with the external data through many types of applications. The Business Connectivity Services feature set enables rapid development and deployment of scalable and security-rich solutions.
The following are some of the features of Business Connectivity Services.
Write-back to External Systems
________________________________________
Using Business Connectivity Services, you can create, read, update, delete, and query (CRUDQ) to the external system from a Microsoft Office application or SharePoint site if the external system supports the operations and is modeled appropriately in the Business Data Connectivity (BDC) service.
Familiar UI
________________________________________
External content types provide SharePoint behaviors (such as lists, Web Parts, and profile pages) to external data and services. As a result, users can work in their familiar work environments without needing to learn different (and often proprietary) user interfaces.
More Connectivity Options
________________________________________
The core function of BDC is to provide connectivity support to the following types of external systems:
• Databases
• Web and Windows Communication Foundation (WCF) services
• Microsoft .NET connectivity assemblies
• Custom data sources
Extensible Provider Model
________________________________________
In addition to connectors for the previous list of data sources provided by BDC, BDC provides a pluggable framework with which developers can plug in connectors for new external system types, thus enabling these new data source types to be accessed via the BDC.
Batch and Bulk Operation Support
________________________________________
In Office SharePoint Server 2007, BDC supported only single item operations, such as search. BDC now provides batch and bulk operation support which enable you to read multiple items in a single call thus reducing round trips to the backend dramatically.
Read BLOBs
________________________________________
BDC now supports reading Binary Large Object (BLOB) data. This is useful for streaming BLOBs of data from the external system.
Read and Write-back of Complex Types
________________________________________
BDC now supports dot notation in field names and therefore enables you to read and write complex types.
Life Cycle Management
________________________________________
Business Connectivity Services provides a set of tools to facilitate creation of models and Office 2010 application artifacts, declaratively and by writing code. You can use SharePoint Designer 2010 to rapidly create composite solutions that meet external unit needs without writing code. You can use Visual Studio to create or extend solutions with sophisticated workflows and data that spans structured LOB systems, unstructured SharePoint applications or Microsoft Office applications, and Web 2.0 services.
Enhanced API Set and Extensibility
________________________________________
Developers can use the BDC Runtime object model to write generic applications by using the stereotyped APIs as building blocks. Such generic applications are then assured to work against any external system, including those that are preexisting and those that are yet to be built.
Developers can also write specific applications that make assumptions about the abstract entity model (the fields exposed by these, and the types of the fields).
And with the .NET Assembly Connector, Custom Connector and the pluggable Secure Store Provider, it provides a rich extensibility mechanism for software developers.
3. Client Object Model
________________________________________Microsoft SharePoint Foundation 2010 introduces three new client APIs for interacting with SharePoint sites: from a .NET managed application (not earlier than Microsoft .NET Framework 3.5), from a Microsoft Silverlight application (not earlier than Silverlight 2.0), or from ECMAScript (JavaScript, JScript) that executes in the browser. These new APIs provide access to a subset of the types and members that are contained in the Microsoft.SharePoint namespace of the server-side object model.
The new client object models provide an object-oriented system for interoperating with SharePoint data from a remote computer, and they are in many respects easier to use than the already existing SharePoint Foundation Web services. You start by retrieving a client context object that represents the current request context, and through this context, you can obtain access to client objects at site-collection level or lower in the SharePoint Foundation hierarchy. Client objects inherit from the ClientObject class (ECMAScript: ClientObject), and you can use them to retrieve properties for a specific SharePoint object, to retrieve child objects and their properties, or to retrieve child items from a collection.
4 Custom Field Rendering Enhancements
Microsoft SharePoint Foundation 2010 makes two significant changes to the way that you define how custom field types render.
XSLT Stylesheet Rendering on List Views
________________________________________
In Windows SharePoint Services 3.0, fields were rendered on list view pages by a RenderPattern element in a field definition file, fldtypes*.xml. In SharePoint Foundation 2010, fields are rendered on list view pages by XSLT stylesheets. Consequently, you now define the rendering of your custom field types by creating a custom XSLT stylesheet rather than adding a custom RenderPattern element to a field type definition. See How to: Create a Custom Field Type Definition and Understanding the FldTypes.xml File for more information about field type definitions. See Overview of XSLT List View Rendering System and How to: Customize the Rendering of a Field on a List View for more information about XSLT rendering and how to customize it.
RenderPattern Elements are Now Obsolete
________________________________________
In Windows SharePoint Services 3.0, fields were also typically rendered in Display mode by means of a RenderPattern element in a field definition file. It was also possible, although rare, to render a field in Edit and New modes with a RenderPattern element. It was more common to render fields in Edit and New modes with a user control (ASCX), known as a RenderingTemplate, and it was possible to use a user control to render a field in Display mode. In SharePoint Foundation 2010, custom fields should always be rendered with user controls in all three modes. Although some long-standing built-in fields still use a RenderPattern element, for development of custom fields RenderPattern elements are obsolete.
PropertySchema Elements are Now Obsolete
________________________________________
In Windows SharePoint Services 3.0, when a custom field had a variable property (that is, a property with a different value on different lists), a control was needed on the New Site Column, Change Site Column, Create Column, and Change Column pages so that users could set the property value. One of the ways that custom field designers could define the rendering of this control was with a PropertySchema element in a field definition file. This method is now obsolete. You should create an editing control as a user control (ASCX). Point your custom field to the user control by setting the FieldEditorUserControl property. For more information about such editor controls, see Custom Field Type Property Rendering and How to: Create an Editor Control for a Field Type Property.
Backward Compatibility
________________________________________
If there is no user control (RenderingTemplate) for a field, the runtime looks for a RenderPattern element in the field type definition file and, if found, uses it. One implication of this behavior is that custom fields that you created for versions earlier than SharePoint Foundation 2010 can still use their existing field type definitions with RenderPattern elements for Display, Edit, or New mode.
SharePoint Foundation 2010 will not automatically render your legacy custom fields on list views by using the Render Pattern in the field type definition for the field. However, if you do not want the default rendering that is given to the field by the XSLT stylesheet, you can re-enable the RenderPattern by adding a
No comments:
Post a Comment