Monday, September 3, 2012

Elements of a SharePoint Solution


Elements of a SharePoint Solution.

The following items are the basic elements of any SharePoint solutions:
  • The project file
  • Project properties
  • References
  • Features folder
  • Package folder
  • Key file (strong-named key)
Solution Explorer showing Elements of SharePoint Solution
Elements of SharePoint Solution
Features Node
  • Contains one or more SharePoint project Features
  • A Feature is a ‘container’ for an additional function to SharePoint
  • Deployed to a specific scope
  • Scope can be : Farm, Web Application, Site (Collection), Web (site)
  • Project items added are also added to the feature node
  • Double-clicking the feature node displays the Feature Designer
  • Feature Designer
    • Creates Features
    • Sets Scopes
    • Establish Feature Dependencies
    • Manually edit the Feature Manifest
    • Overriding the generated manifest will disable the Designer, and then all further changes will need to be done manually
Package Node
  • Groups and view the hierarchical Package tree
  • Groups the SharePoint Items into a Solution Package
  • The Package node contains a single file that serves as the distribution mechanism for the SharePoint project.
  • This Package file is also known as a solution package, is .CAB-based with a .WSP extension.
  • A solution package is a deployable, reusable file that contains a set of features, site definitions, and assemblies that apply to SharePoint sites, and that you can enable or disable individually.
  • The Package node also always contains a file that is named Package.wspdef, an XML definition file for the package.
  • Once a package is deployed to the SharePoint server, the SharePoint administrator can install it and activate its features.
  • Double-clicking the Package node opens it in the Package Designer. You can then view or change its contents.
Key file (strong-named key)
  • Assembly signing (also called strong-name signing) gives an application or component a unique identity that other software can use to identify and refer explicitly to it.
  • A strong name consists of its simple text name, version number, culture information (if provided), plus a public/private key pair.
  • For the purpose of assembly signing, Visual Studio supports only Personal Information Exchange (.pfx) and Strong Name Key (.snk) files stored in the project system on the local computer.


No comments: