| Term | Definition |
|---|---|
| access control entry | An entry in either a securable object's discretionary access control list (DACL) or an object's system access control list (SACL). In a DACL, the entry grants or denies permissions to a user or group. In a SACL, the entry specifies which security events to audit for a particular user or group or controls the Windows Integrity Level for the object. |
| access control list | In Windows-based systems, a list of access control entries (ACE) that apply to an entire object, a set of the object's properties, or an individual property of an object, and that define the access granted to one or more security principals. |
| access URL | The internal URL that is used by a crawler to identify and access an item. |
| ACE | An entry in either a securable object's discretionary access control list (DACL) or an object's system access control list (SACL). In a DACL, the entry grants or denies permissions to a user or group. In a SACL, the entry specifies which security events to audit for a particular user or group or controls the Windows Integrity Level for the object. |
| ACL | In Windows-based systems, a list of access control entries (ACE) that apply to an entire object, a set of the object's properties, or an individual property of an object, and that define the access granted to one or more security principals. |
| activity feed | A feed that provides information, notifications and updates based on people, documents, and tags you are following. |
| activity flow | A running instance of a workflow that consists of a sequence of action instances and/or activity model instances. Action instances and activity model instances can be sequenced in any order to create a single activity flow. |
| activity model | A predefined sequence of actions. |
| after event | An asynchronous event whose handler runs only after the action that raised the event is complete. |
| alert subscription | A request to receive an Internet message automatically when user-defined criteria are met. Such messages are generated automatically when items such as documents, Web pages, list items, sites, or other resources on a server are changed. |
| alternate account | An additional user account that is in a different domain, but within the same forest as the primary account. |
| application directory | The directory on an index server or a query server where all files are stored for the purpose of creating a full-text index catalog or performing queries on a full-text index catalog. |
| application session | The period of time when an application is running. When an application starts, the session starts. When an application quits, the session ends. |
| audience identifier | A GUID or string that is used to uniquely identify an audience. |
| audience rule | A set of logical conditions that determine whether a user profile can be a member of an audience. |
| authoritative page | A Web page that a site collection administrator has designated as more relevant than other Web pages. This is typically the URL of the home page for the intranet of an organization. The higher the authority level assigned to a page, the higher the page appears in search results. Also referred to as authoritative page. |
| authority level | A floating-point number that designates that a specific Web page is more relevant than other Web pages. Allowed values are 0, 1, or 2. Zero (0) signifies the most valuable authoritative page level. |
| authority page | A Web page that a site collection administrator has designated as more relevant than other Web pages. This is typically the URL of the home page for the intranet of an organization. The higher the authority level assigned to a page, the higher the page appears in search results. Also referred to as authoritative page. |
| available site template | An XML-based collection of predefined or user-defined settings that are stored as a site definition configuration or a site template, and can be used when creating a site. |
| backward signing | A condition of a handwritten signature, in an image or .ink file, that specifies the direction of the characters in the signature, right-to-left or left-to-right. |
| base view identifier | An integer that uniquely identifies a view definition for a list. |
| basic page | A Web Parts page that contains only one Web Part zone and, by default, a Content Editor Web Part. |
| BCS | A feature that enables users to interact with back-end (LOB) data from within the Office Suite and SharePoint. |
| BCS solution deployment | BCS server to client solution deployment that is based on ClickOnce technology. |
| before event | A synchronous event whose handler runs completely before the action that raised the event starts. |
| blank site | A site that was created by using the "Blank" site template. |
| Business Connectivity | A feature that enables users to interact with back-end (LOB) data from within the Office Suite and SharePoint. |
| Business Connectivity Services | A feature that enables users to interact with back-end (LOB) data from within the Office Suite and SharePoint. |
| CAML | An XML-based language that is used to describe various elements, such as queries and views, in sites that are based on Microsoft® SharePoint® Products and Technologies. |
| Central Administration site | A special SharePoint site where an administrator can manage all sites and servers in a farm that is running Microsoft® SharePoint® Products and Technologies. |
| Collaborative Application Markup Language | An XML-based language that is used to describe various elements, such as queries and views, in sites that are based on Microsoft® SharePoint® Products and Technologies. |
| content migration package | A package of XML-formatted files that is used to migrate content between site collections, sites, and lists. |
| content placeholder | A region within a page layout that is populated dynamically with the value of the publishing page field to which it is bound. |
| content type group | A named category of content types that is used to organize content types of a similar purpose. |
| content type identifier | A unique identifier that is assigned to a content type. |
| content type order | The sequence in which content types are displayed. |
| content type resource folder | A folder that stores the resource files that are associated with a content type. |
| content type schema | An XML definition that describes the contents of a content type. |
| content type specific view | A view that is associated with a particular content type that is associated with a folder. |
| context site | A site that corresponds to the context of the current request. |
| context type | A GUID that is used as a classification for an event receiver. |
| contextual search scope | A system-defined restriction that can optionally be added to a query to restrict the query results to items that are from a specific site or list. |
| crawl log | A set of properties that provides information about the results of crawling a display URL. The information includes whether the crawl was successful, the content source to which the display URL belongs, and the level, message, time, and identifier for any errors that occur. |
| crawl queue | A data structure that stores the list of items to crawl next. |
| crawled property | A type of metadata that can be discovered during a crawl and applied to one or more items. It can be mapped to a managed property. |
| Data View Web Part | A Web Part that is used to display items in a list. |
| declarative workflow association | A code-free binding of a declarative workflow to a specific list or content type using XAML (Extensible Application Markup Language). |
| default list view | The view of a list that is defined by the owner of the list to appear when users browse to the list without specifying a view. |
| default mobile list view | The view of a list that is defined by the owner of the list to appear when users browse to the list from a mobile device without specifying a view. |
| default search scope | The search scope that is assigned automatically to a search scope display group. |
| default user store | A user store supplied as a starting point for expanding group membership when a user store is not already specified in FAST Search Authorization. |
| deployment system object | An object that is created as part of a site or site collection. Examples of deployment system objects are root folders, catalogs, default pages, and galleries that are created during site or site collection creation. A deployment system object is not part of a template. |
| descendant content type | Any content type that inherits from another content type. |
| dynamic rank | A component of the rank that depends on how well query text matches an indexed item. |
| excluded item | An item that is excluded from a crawl by the administrator of the host site or the search administrator of the crawler. |
| extracted definition | The definition that is obtained by an index server during a crawl, to identify if any sentences in the item match the pattern for defining a term. |
| extracted term | A term that an extracted definition applies to. |
| Farm Administrators group | A group of users that has permission to manage all of the servers in a server farm. Members of the Farm Administrators group can perform command-line operations and all of the administrative tasks in Central Administration for the server or server farm. |
| farm solution | A custom solution that can be deployed to a farm by a farm administrator. A farm solution has full access to system resources and other sites in the farm. |
| feature definition | An XML fragment that defines a feature and its attributes. |
| feature identifier | A GUID that identifies a feature. |
| feature property | A property that is associated with an active feature at a particular scope. |
| feature scope | The scope at which a feature can be activated. |
| federated location | A source that returns a set of search results for a given search query. The source can be a search service in the local server farm or another server farm, or another search engine that is compliant with the OpenSearch protocol. |
| federated location definition | The configuration settings that describe how to issue a query for a given federated location and display the search results. |
| field internal name | A string that uniquely identifies a field in a content type or a SharePoint list. |
| first-stage Recycle Bin | A container for items that are deleted. Items in this container are visible to users with the appropriate permissions and to site collection administrators. |
| FSA Manager | The Windows service that provides administration functionality for FAST Search Authorization. |
| FSA worker | The Windows service that generates user search security filters in FAST Search Authorization. |
| full-text index component | A set of files that contain all index keys that are extracted from a set of items. |
| generic list | A list whose base type is Generic List. |
| Group Approval document identifier | A string that uniquely identifies a document that is subject to the policies defined for a Group Approval workflow. The string is generated and assigned automatically to a document by a protocol server. |
| high confidence property | A managed property from the metadata index that the administrator identifies as a good indicator of a highly relevant item. It is used to produce a high confidence result. |
| high confidence result | A search result that is considered to be highly relevant because of a precise match between a high confidence property value and the tokens in the query text. |
| item identifier | An integer that uniquely identifies an item in a SharePoint list. |
| keyword consumer | A site collection that uses a particular set of keywords, synonyms, and Best Bets. |
| keyword synonym | An alternate phrasing of a particular keyword. When a user types a keyword synonym, search returns the same Best Bet result as the keyword. |
| language auto-detection | A process that automatically determines the language code identifier (LCID) for text in a document. |
| list folder | A folder that is contained within a SharePoint list. A list folder can contain documents or list items, and it retains the characteristics of other items in the list, such as a customizable schema. |
| list form | A page that allows users to create, view, or edit an item in a list. |
| List Form Web Part | A Web Part that is used to display, edit, or view an item in a list. |
| list identifier | A GUID that is used to identify a list in a site collection. |
| list item attachment | A file contained within a list item that is stored in a folder in the list with the segment “Attachments." |
| list item identifier | An integer that uniquely identifies an item in a SharePoint list. |
| list server template | A value that identifies the template that is used for a list. |
| list template | An XML-based definition of list settings, including fields and views, and optionally list items. List templates are stored in .stp files in the content database. |
| list template identifier | A GUID that is used to identify a list template. |
| list view page | A Web Part Page that displays a view of a list. |
| List View Web Part | A reusable component that generates HTML-based views of items in a SharePoint list. |
| log level | The amount of information that is stored in a log file for a transaction. Log levels can be represented by numbers or by words from the most to the least verbose. |
| managed keyword | A word or phrase that is added to a SharePoint item, either as a value in the Managed Keyword column or as a social tag. |
| member group | A group of users that is specific to the User Profile service. |
| member group source | A qualified domain name, such as domain.corp.microsoft.com, that identifies the source of a member group. |
| Members group | A default group of users on a SharePoint site. By default, the Members group is assigned the Contribute permission level. |
| membership group record identifier | A unique identifier for a member group record. |
| metadata index | A data structure on a back-end database server that stores properties that are associated with each item, and attributes of those properties. |
| metadata schema | A schema that is used to manage information about an item. |
| Microsoft Business Connectivity Services | A feature that enables users to interact with back-end (LOB) data from within the Office Suite and SharePoint. |
| moderated object | An object for which a moderator reviews and either approves or rejects additions or changes to that object. New objects and changes to existing objects can be seen by other users only after they have been approved by the moderator. |
| moderation status | A content approval status of an item in a list. |
| multivalue property | A property that can contain multiple values of the same variant type. |
| navigation structure | A hierarchical organization of links between related content, such as lists within a site. |
| new form | A form that allows for the creation of a list item. |
| Office SharePoint Server Search service | The farm-wide service that either responds to query requests from front-end Web servers or crawls items. |
| Open Item permission | An authorization that allows a user to retrieve an entire file. |
| Open Web permission | A requisite permission during the import or export of a SharePoint site. |
| operator account | The account of the user who is managing the import process for a deployment package. |
| organization identifier | An integer that uniquely identifies an organization. |
| orphaned object | A content database object that lacks a requisite relationship to a corresponding object. |
| paged view | A view that supports one or more visual pages. A paged view is used to break up large sets of data into smaller sets for increased performance and manageability. |
| parent farm | A farm that crawls content from another farm and also responds to query requests from that farm. |
| parent list | A list that contains a list item or list folder. |
| PerformancePoint Data Connections Library | A SharePoint document library that contains PerformancePoint data sources. |
| personal site | A type of SharePoint site that is used by an individual user for personal productivity. The site appears to the user as My Site. |
| portal content | The main search catalog, which contains content sources and settings that are related to a crawl. |
| principal aliasing | The process of mapping a user or a group in one user store to a user or a group in another user store for the purpose of returning all documents that the user or group has rights to view, regardless of which user store the user or group is authenticated to. |
| privacy level | A setting that specifies the category of users who are allowed to view the personal information of other users, such as user profile properties, colleagues, or memberships. |
| provisioned | A condition of an object that was created and deployed successfully. |
| public filter | The search security filter in FSA that finds documents that all users have access to. |
| publish to server | A process that facilitates saving a document or portions of a document to a Web server. |
| published version | The version of a list item that is approved and can be seen by all users. The user interface (UI) version number for a published version is incremented to the next positive major version number and the minor version is zero. and minor version. |
| publishing level | An integer that is assigned to a document to indicate the publishing status of that version of the document. |
| publishing page | A document that binds to a page layout to generate an HTML page for display to a reader. Publishing pages have specific fields that contain the content that is displayed in an HTML page. |
| query independent rank | A system to rank items that uses features that do not vary with different queries. |
| query table | A two-dimensional table that presents data from an external data source. |
| ranking parameter | A value that is used to influence the algorithm that determines the rank of an item. |
| role identifier | An integer that uniquely identifies a role definition within a site. |
| role type | A predefined role definition. |
| root document | A document in the root folder of a site. |
| scheduled | A status that is applied to a list item or document that specifies a time when the item or document will be published or unpublished. |
| schema version | An integer value that represents the version number of the schema for a deployment package. |
| search application | A unique group of search settings that is associated, one-to-one, with a shared service provider. |
| search catalog | All of the crawl data that is associated with a given search application. A search catalog provides information that is used to generate query results. |
| search database | A database that stores search-related information, including stored procedures and tables that are used for crawler data, document metadata, and administration information. |
| search query log | A record of information about user searches, such as search terms and time of access. |
| search scope consumer | A site collection that uses a particular search scope display group. |
| search scope display group | An ordered set of search scopes, defined by an administrator or programmatically, and used for returning groups of search scopes. Search scope display groups are saved for each search scope consumer and search scopes can be in multiple search scope display groups. |
| search scope index | A specialized component of a full-text index catalog that is built on the values of scoped properties for optimized queries. |
| search scope rule | An attribute that specifies which items are included in a given search scope. |
| search service account | A user account under which the search service runs. |
| search shared application object | An instance of a shared application for search that holds search-specific settings. |
| second-stage Recycle Bin | A container for items that have been deleted from a first-stage Recycle Bin. Items in a second-stage Recycle Bin are visible only to site collection administrators. |
| Shared Documents library | A document library that is included by default in the Team Site site template. |
| shared view | A view of a list or Web Part Page that every user who has the appropriate permissions can see. |
| SharePoint Search SQL syntax | The rules that govern the construction of an enterprise search SQL query. |
| single sign-on ticket | A token that contains the encrypted identity of a single sign-on (SSO) user in the form of a security identifier string and a nonce. |
| site collection administrator | A user who has administrative permissions for a site collection. |
| site collection flag | A 4-byte unsigned integer bit mask that specifies the properties that are global to a site collection. One or more values can be set for this bit mask. |
| site collection identifier | A GUID that identifies a site collection. In stored procedures, the identifier is typically @SiteId or @WebSiteId. In databases, the identifier is typically SiteId/tp_SiteId. |
| site collection quota | An option for a site collection that allows administrators to set levels for maximum storage allowed, maximum number of users allowed, and warnings that are associated with the maximum levels. |
| site column | A field that can be associated with a content type or list within a site or site collection. |
| site content type | A named and uniquely identifiable collection of settings and fields that store metadata for lists within individual sites. |
| site definition | A family of site definition configurations. Each site definition specifies a name and contains a list of the site definition configurations. |
| site definition configuration | An XML-based definition of lists, features, modules, and other data, that collectively define a type of SharePoint site. Site definition configurations are stored in the ONET.xml file. |
| site definition version | A zero-based integer that indicates the version number of the site definition. Every time a site definition is updated, it is suggested that the version number be increased. |
| site flag | A 4-byte unsigned integer bit mask that specifies properties that are unique to a site. |
| site identifier | A GUID that is used to identify a site in a SharePoint site collection. |
| site membership | The status of being a member of a site and having a defined set of user rights for accessing or managing content on that site. |
| site property | A name/value pair of strings that serves as metadata for a site, such as the title or default language. |
| site solution | A deployable, reusable package that contains a set of features, site definitions, and assemblies that apply to sites, and that can be enabled or disabled individually. |
| site template | An XML-based definition of site settings, including formatting, lists, views, and elements such as text, graphics, page layout, and styles. Site templates are stored in .stp files in the content database. |
| start address | A URL that identifies a point at which to start a crawl. Administrators specify start addresses when they create or edit a content source. |
| static rank | The component of a rank that does not depend on the search query. It represents the perceived importance of an item and may be related to the origin of the item and relationships between the item and other items or business rules that are defined in the search application. |
| trusted authentication | A mechanism whereby a user account or a process account can be used to perform operations on behalf of the current user. |
| trusted subsystem | A method of communication in which two-way trust is established between two server components. Each server component communicates with the other component by using an account that is authorized to perform privileged actions such as retrieving files and settings. |
| UI culture | The language that is used to display strings and other graphical elements in a user interface. |
| user display name | A user profile property that can contain the preferred name of a user. |
| user profile change entry log | A repository that logs all of the changes that take place in a user profile. |
| user profile change event | An event that occurs when a property of any user profile is changed. |
| user profile import | The process of importing records from a directory service to the user profile store. |
| user profile record identifier | An integer that uniquely identifies a user profile record. |
| user profile store | A database that stores information about each user profile. |
| user search security filter | The user search security filter that specifies group and user permissions for a specific FAST Search user. FAST Search Authorization (FSA) filters out inappropriate search results by intersecting the user’s query with the user's search security filter, and checking each document’s access control list to determine if the user has permission to view that document. The user search security filter is FSA's primary means of enforcing document-level security ("security trimming"), which helps to ensure that search results display only documents that the user has permissions to read. |
| user store | A logical grouping of users, groups, and content permissions for a third-party security or content system that is accessed by FAST Search Authorization. |
| visible scope | A search scope that is displayed to site collection administrators and users. |
| Visitors group | A default group of users on a SharePoint site. By default, the Visitors group is assigned the Read permission level. |
| Web application identifier | A GUID that identifies a Web application. |
| Web control | A server-side component that encapsulates user interface and related functionality. |
| Web discussion comment | An individual comment that is added within a Web discussion. |
| Web identifier | A GUID that is used to identify a site in a SharePoint site collection. |
| Web Part cache | A hash table of key/value pairs that is used to cache and locate internal information for Web Parts. |
| Web Part chrome state | The condition of a Web Part and the Web Part chrome surrounding it. Possible values are zero (0) for normal state or one (1) for minimized state. |
| Web Part connection | An element in a Web Parts page that defines a provider-consumer data relationship between two Web Parts. When a Web Parts page is rendered, data provided by one Web Part can affect how and what is rendered by the other Web Part. |
| Web Part identifier | A GUID that identifies a Web Part. |
| Web Part property | A configurable characteristic of a Web Part that determines the behavior of the Web Part. |
| Web Part type identifier | A unique 16-byte value that is assigned to each Web Part type. |
| Web Part zone identifier | A string that identifies a Web Part zone on a Web Parts page. |
| Web Part zone index | An integer that specifies the relative position of a Web Part in a Web Part zone. Web Parts are positioned from the smallest to the largest zone index. If two or more Web Parts have the same zone index, they are positioned adjacent to each other in an undefined order. |
| Web service method | A procedure that is exposed to Web service clients as an operation that can be called on the Web service. |
| work item process | A process that runs a work item. |
| work item type identifier | A GUID that is used to identify a work item type. |
| workflow association | An association of a workflow template to a specific list or content type. |
| workflow configuration file | An implementation-specific file that is a part of a workflow. The workflow configuration file contains information that is necessary to create a workflow template from the specified workflow markup and rules files, and to associate it to a specific list. |
| workflow history item | A list item that stores information about the current status of, and past actions for, a document or item that is associated with a workflow. |
| workflow history list | A list that stores the history of actions or tasks for a business process. |
| workflow identifier | A GUID that is used to identify a workflow. |
| workflow markup file | A file that contains markup to specify the functional behavior of a workflow. |
| workflow task | An action or task in a sequence that is related to a built-in or user-defined business process. |
| workflow task list | A list that stores the sequence of actions or tasks for a business process. |
| zero-based index | An index in which the first item has an index of zero. |
Tuesday, July 17, 2012
Terms and Definitions In SharePoint 2013
Application Services
SharePoint Server 2013 Preview includes several services for working with data in your SharePoint sites. New for SharePoint is the Machine Translation Service, which translates sites, documents, and streams for multilingual support. SharePoint Server 2013 Preview also includes Access Services and a new data access model. For converting files and streams to other formats, SharePoint Server 2013 Preview has Word Automation Services and PowerPoint Automation Services (a new feature for SharePoint). SharePoint also provides data analysis tools, like PerformancePoint Services and Visio Services, that enable business intelligence, and powerful new features in Excel Services.
Business Connectivity Services
Business Connectivity Services (BCS) enables SharePoint to access data from external data systems such as SAP, ERP, and CRM, in addition to other data-driven applications that are exposed through WCF services or OData endpoints. BCS in SharePoint 2013 Preview has been improved and enhanced in many ways, including OData connectivity, external events, external data in apps, filtering and sorting, support for REST, and others.
Enterprise Content Management
In SharePoint 2013 Preview, you can now use .NET client, Silverlight, Windows Phone, and JavaScript APIs, in addition to the newly expanded set of .NET server managed APIs, to customize Enterprise Content Management (ECM) experiences and behavior.
Workflows
Windows Azure Workflow is a redesigned workflow infrastructure that is built on Windows Workflow Foundation 4 and brings new power and flexibility to workflow authoring in SharePoint 2013 Preview. A fully declarative authoring environment enables information workers to use SharePoint Designer 2013 Preview to author powerful workflows, and a new set of Visual Studio 2012 workflow project templates let developers access more sophisticated features like custom actions. Perhaps most importantly, Windows Azure Workflow is fully integrated with the model for apps for SharePoint. In addition, workflows execute in the cloud, not in SharePoint, which provides enormous flexibility in designing workflow-based apps for SharePoint.
Search
Search functionality in SharePoint 2013 Preview includes several enhancements, custom content processing with the Content Enrichment web service, and a new framework for presenting search result types. Additionally, there have been significant enhancements made to the keyword query language (KQL).
Social and Collaboration
New and improved social and collaboration features make it easy for users to communicate and to stay engaged and informed. The improved My Site social feed helps users keep up to date with the people and content that they care about. The new Community Site feature provides a rich community experience that lets users easily find and share information and find people who have similar interests.
Mobility
With SharePoint 2013 Preview, you can combine Windows Phone 7 applications with on-premises SharePoint services and applications, or with remote SharePoint services and applications that run in the cloud (such as those that use SharePoint Online), to create powerful applications that extend functionality beyond the traditional desktop or laptop and into a truly portable and much more accessible environment. The new mobility features in SharePoint 2013 Preview are built on existing Microsoft tools and technologies, such as SharePoint, Windows Phone 7, Visual Studio, and Microsoft Silverlight. You can create SharePoint-powered mobile applications for Windows Phone using the new SharePoint phone application wizard template in Visual Studio, which lets you create simple list-based mobile applications. You can integrate new features introduced in SharePoint 2013 Preview, such as the Geolocation field type and “push" notifications from SharePoint Server, into your mobile applications.
Core Platform Enhancements
On a broader scale, SharePoint 2013 Preview has been improved and enhanced to support the new cloud-based architecture and app-driven development framework. From the SharePoint APIs at the lowest level to connectivity to social media integration, SharePoint 2013 Preview is designed and executed to support a rich application development experience. In addition to the use of Representational State Transfer (REST) endpoints for web services, there is a broad new API for both server and client development. Remote event receivers and now supported in addition to client-side rendering.
Development Tools
The current release reflects enormous strides in optimizing the existing development tools like Visual Studio and SharePoint Designer, in addition to providing the release of newly developed web-based tool "Napa" Office 365 Development Tools for developing apps. The new unified project system in Visual Studio lets you develop apps for SharePoint, apps for Office, apps for SharePoint that include apps for Office, or apps for Office that are hosted by SharePoint. In addition to the SharePoint project templates that were provided in earlier versions, Visual Studio 2012 now includes a new app project template in the Apps folder named Apps for SharePoint 2013. Several new properties have been added to the Properties window and Properties pages to support app for SharePoint projects. Other improvements include full support for development against the Cloud App Model, including OData and OAuth support, and full support for development against the Windows Azure Workflow platform.
Familiar Programming Model using Web Standards
SharePoint 2013 Preview makes it easy for any web developer, including those who work on non-Microsoft platform stacks, to create SharePoint solutions. What makes this possible is that SharePoint 2013 Preview is based on common web standards like HTML, CSS, and JavaScript. Furthermore, implementation relies on established protocols like the Open Data protocol (OData), and OAuth.
Cloud App Model
SharePoint 2013 Preview introduces a Cloud App Model that enables you to create apps. Apps for SharePoint are self-contained pieces of functionality that extend the capabilities of a SharePoint website. An app may include SharePoint components such as lists, workflows, and site pages, but it can also surface a remote web application and remote data in SharePoint. An app has few or no dependencies on any other software on the device or platform where it is installed, other than what is built into the platform. This characteristic enables apps to be installed simply and uninstalled cleanly. Apps have no custom code that runs on the SharePoint servers. Instead, all custom logic moves "up" to the cloud or "down" to client computers. Additionally, SharePoint 2013 Preview introduces an innovative delivery model for apps for SharePoint that includes components like the SharePoint Store and the App Catalog.
What's New in SharePoint 2013
- Cloud App Model
- Familiar Programming using Web Standards
- Development Tools
- Core Platform Enhancements
- Mobility
- Social and Collaboration
- Business Connectivity Services
- Enterprise Content Management
- Search
- Application Services
SharePoint 2013 Released
HI All,
SharePoint 2013 Released By Microsoft. For more information please go through the links i had posted in my Blog.
SharePoint 2013 Released By Microsoft. For more information please go through the links i had posted in my Blog.
Monday, July 16, 2012
How to Refresh the Second WebPart without using Connectable webparts.
This is a requirement in an Interview for one of my friend. First Take two user controls. In First User Control Add the Controls u want and now add the second user control as a control and write the following code in WebPart1.
Procedure:-
Add one Sample Project with Name Sample001. Now Add two Visual WebParts with Names WebPart001 & WebPart002.
In WebPart Ascx Page write the below HTML.
Procedure:-
Add one Sample Project with Name Sample001. Now Add two Visual WebParts with Names WebPart001 & WebPart002.
In WebPart Ascx Page write the below HTML.
WebPart001 Ascx |
<%@ Assembly Name="$SharePoint.Project.AssemblyFullName$" %> <%@ Assembly Name="Microsoft.Web.CommandUI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ Register Tagprefix="Utilities" Namespace="Microsoft.SharePoint.Utilities" Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ Register Tagprefix="asp" Namespace="System.Web.UI" Assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" %> <%@ Import Namespace="Microsoft.SharePoint" %> <%@ Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ Control Language="C#" AutoEventWireup="true" CodeBehind="WebPart001UserControl.ascx.cs" Inherits="Sample001.WebPart001.WebPart001UserControl" %> <%@ Register src="../WebPart002/WebPart002UserControl.ascx" tagname="WebPart002UserControl" tagprefix="uc1" %> <table width="100%" cellpadding="0" cellspacing="0"> <tr> <td valign="top"> <table cellpadding="0" cellspacing="0"> <tr><td>Enter Employee ID</td><td><asp:TextBox ID="txtEmpID" runat="server"></asp:TextBox></td></tr> <tr><td>Enter Employee Name</td><td><asp:TextBox ID="txtEmpName" runat="server"></asp:TextBox></td></tr> <tr><td colspan="2" align="center"><asp:Button ID="btnSave" Text="Save" runat="server" onclick="btnSave_Click" /></td></tr> <tr><td colspan="2" align="center"><asp:Label ID="lblErrorMessage" runat="server"></asp:Label></td></tr> </table> </td> <td valign="top"> <div id="divGrid" height="300px" style="scroll:auto;"><uc1:WebPart002UserControl ID="WebPart002UserControl1" runat="server" /></div> </td> </tr> </table> |
WebPart001 Ascx Load |
using System; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using Microsoft.SharePoint; using Microsoft.SharePoint.WebControls; using System.Security; using WP2=Sample001.WebPart002; namespace Sample001.WebPart001 { public partial class WebPart001UserControl : UserControl { protected void Page_Load(object sender, EventArgs e) { } protected void btnSave_Click(object sender, EventArgs e) { try { SPWeb currentWeb = SPContext.Current.Web; SPList lst = currentWeb.Lists["Employee"]; SPListItemCollection myColl = lst.Items; SPSecurity.RunWithElevatedPrivileges(delegate() { SPListItem item = myColl.Add(); item["EmpID"] = txtEmpID.Text; item["EmpName"] = txtEmpName.Text; item.Update(); txtEmpID.Text = ""; txtEmpName.Text = ""; }); SPGridView sgv = (SPGridView)WebPart002UserControl1.FindControl("sgvEmployee"); sgv.DataSource = myColl.GetDataTable(); sgv.DataBind(); } catch (Exception ex) { lblErrorMessage.Text = ex.ToString(); } } } } |
WebPart002 Ascx |
<%@ Assembly Name="$SharePoint.Project.AssemblyFullName$" %> <%@ Assembly Name="Microsoft.Web.CommandUI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ Register Tagprefix="Utilities" Namespace="Microsoft.SharePoint.Utilities" Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ Register Tagprefix="asp" Namespace="System.Web.UI" Assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" %> <%@ Import Namespace="Microsoft.SharePoint" %> <%@ Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ Control Language="C#" AutoEventWireup="true" CodeBehind="WebPart002UserControl.ascx.cs" Inherits="Sample001.WebPart002.WebPart002UserControl" %> <table width="100%" cellpadding="0" cellspacing="0"> <tr> <td> <SharePoint:SpGridView ID="sgvEmployee" runat="server" AutoGenerateColumns="false"> <Columns> <asp:BoundField HeaderText="Employee ID" DataField="EmpID" /> <asp:BoundField HeaderText="Employee Name" DataField="EmpName" /> </Columns> </SharePoint:SpGridView> </td> </tr> </table> |
WebPart002 Ascx Load |
using System; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using Microsoft.SharePoint; using System.Data; namespace Sample001.WebPart002 { public partial class WebPart002UserControl : UserControl { protected void Page_Load(object sender, EventArgs e) { if (!IsPostBack) { getData(); } } public void getData() { SPWeb currentWeb1 = SPContext.Current.Web; SPList lst1 = currentWeb1.Lists["Employee"]; SPListItemCollection myColl1 = lst1.Items; if (myColl1.Count > 0) { sgvEmployee.DataSource = myColl1.GetDataTable(); sgvEmployee.DataBind(); } } } } |
Subscribe to:
Posts (Atom)
