Skip to main content

Types of Features in SharePoint 2013

Image
By
  • Feature/Site Template Association: Allow to associate new features and functionality with existing site definition configuration feature automatically included in the provisioning(Microsoft). 
    • Can Associate the feature with Global Site template (event receiver to the site creation to write your custom code)
    • Provide a Feature “Stapling”
    • Attach a feature to existing site template
    • Facilitating a versioning and reusability
      • <FeatureSiteTemplateAssociation Id="29D85C25-170C-4df9-A641-12DB0B9D4130" TemplateName="STS#0" />
  • Data structure of SharePoint Site : Site Column and Content type
    • Field : Creates the custom fields
      • <Field ID="string" Name="string" Type="string">mixed</Field>
    • Content Type: Create the content type.
      • <ContentType>mixed</ContentType>
    • Content Type Binding: Associate the content type with list.
      • <ContentTypeBinding />
  • List/Libraries Features : 
    • List Template (once you create the list template you able to create the list instance to create the list)
      • <ListTemplate>mixed</ListTemplate>
    • List Instance: Define a instance of a list
      • <ListInstance Title="string">mixed</ListInstance>
  • WorkFlow
    • WorkFlow : Register the .Net code to the SharePoint Site.
      • <Workflow>mixed</Workflow>
    • WorkFlow Association (Mostly done with dot net code): register the workflow with the particular list and libraries. Example approval workflow etc. You can do the workflow using .Net Code.
      • <WorkflowAssociation />
      • <WorkflowActions4></WorkflowActions4> (2013)
  • Receiver Feature element: Attached the .Net Code with SharePoint list, libraries and webs.
    • <Receivers><Receiver></Receiver>mixed</Receivers>
  • Content
    • Control (delegate Control) Search Control
      • <Control>mixed</Control>
    • Module (deploy the files)
      • <Module>mixed</Module>
  • Custom Action: modifies the specific are of the SharePoint Page. Site settings pages links, item custom actions and ribbon.
    • Custom Action Group
      • <CustomActionGroup>mixed</CustomActionGroup>
    • Custom Action: 
      • <CustomAction>mixed</CustomAction>
    • Hide Custom Action : Hide some links and replace with your custom action links
      • <HideCustomAction>mixed</HideCustomAction>
  • Property Bag: Specifies the properties in the property bag for the list item, file, folder, or website.
    • <PropertyBag ParentType="Web"></PropertyBag>
  • Web Template:Web Templates are introduced in SharePoint 2010 mainly to define site definition as sandboxed solutions
    • <WebTemplate BaseTemplateID="int" BaseTemplateName="string" BaseConfigurationID="int" Name="string">mixed</WebTemplate>
  • Workflow Action: Create the workflow action that will displays to the SharePoint designer as the Activity and it will show when you create the workflow.
    • <WorkflowActions></WorkflowActions>
  • Web Part Adder Extension: Add web part without .webpart file. I am not found MSDN but good there are two article written by Criso O'Brien and Wictor.
    • <WebPartAdderExtension Assembly="string" Class="string" />
  • User Migrator : Not find any information about this features even in MSDN.
    • <UserMigrator />
  • Group Migrator: Not find any information about this feature even in MSDN.
    • <GroupMigrator />
  • Document Converter (seldom used): used to convert site “word document “to other formats like PDF, HTML etc.
    • <DocumentConverter Id="{guid} Name="DOC to PDF " App="exe file name" From="doc" To="pdf" />
  • ClientWebPart : This is used in SharePoint 2013 App model to display the app as the WebPart. 
    • <ClientWebPart Name="string"><Content Type="html" /></ClientWebPart>
  • EmailTemplate: Not found any information about this feature even in MSDN.
    • <EmailTemplate TemplateFile="" Description="" Id="" Locale="" Sequence="" Title="" />
  • BdcModel: This feature used to create the Bdc Model file. 
    • <BdcModel Path="string"></BdcModel>
Labels:

Comments

Post a Comment

Popular posts from this blog

SharePoint RPC Protocols Examples Using OWSSVR.DLL

By
What is SharePoint RPC Protocols? Part 1 This reference includes information about the methods and usage of SharePoint Foundation Remote Procedure Call (RPC) protocol. This protocol can be used in Win32-based applications or in ASPX applications to make HTTP POST requests to the server. Methods in this protocol that do not modify the contents of the database can also be used in URL protocol to make HTTP GET requests. Definition taken from http://msdn.microsoft.com/en-us/library/ms448359.aspx You will find the OWSSVR.DLL in SharePoint 2010 Server Physical Path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI and MOSS C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI OWSSVR.DLL List of commands DialogView  Display ExportList GetProjSchema GetUsageBlob HitCounter RenderView To read more about the OWSSVR.DLL command Please read the URL Protocol from Microsoft Blog having a URL http://msdn.microsoft.com/en...
1 comment
Read more

SharePoint 2013 Search Database Part 1

By
SharePoint 2013 Search architecture drastically change, as earlier in FS4SP 2010 we have 2 search applications “FASTContentSSA” and “FASTQuerySSA” and 7 total database in use. Following are the List of DB (FS4SP) FASTContentSSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTQuerySSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTSearchAdminDatabase : Fast Search Admin Database  In SharePoint 2013 search has only 1 Search Service application and 4 database in use. No property store database need any more, now the properties are directly stored inside the index component and all the index directly indexed to the physical system where FS4SP data comes from database as well as from the File system now data directly stored and indexed/ retried from the Physical disk because of this performance increase and search experien...
Post a Comment
Read more

STS CryptographicException Error : Key set does not exist

By
Common mistakes Both SharePoint Site and SSO Site NOT running on the same application pool. Application pool identity user doesn’t have permission to access the certification.  Solution to this problem Set the same identity pool to  : 2. Be sure to grant rights to the certificate for the App Pool running the web service Start -> Run -> MMC File -> Add/Remove Snapin Add the Certificates Snap In Select Computer Account, then hit next Select Local Computer (the default), then click Finish On the left panel from Console Root, navigate to Certificates (Local Computer) -> Personal -> Certificates You're certificate will most likely be here. Right click on your certificate -> All Tasks -> Manage Private Keys Set you're private key settings here. Add app pool account Reset iis
Post a Comment
Read more