Changes of 15 hives Folder from 14 hives in SharePoint 2013

The 14 Hive
The 14 Hive is a special folder which is created during Sp 2010 installation. All the important files for supporting Sharepoint framework like web.config, Features, Web Parts, User Controls, Help Files etc are stored in the SharePoint 2010 server file system inside the 14 Hive.

 

The 15 Hive
The 15 Hive is a special folder which is created during SharePoint 2013 installation. All the important files for supporting SharePoint framework like Features, Web Parts, User Controls, Help Files etc are stored in the SharePoint 2013 server file system inside the 15 Hive.

 Only Client folder is new in 15 hives

The 15 Hive – Folder Location
The 15 Hive folder is located at the following path
C:\Program Files\Common files\Microsoft Shared\Web Server Extensions\15

The 15 Hive – Folder Structure
The 15 Hive has a definite folder structure which holds the core SharePoint server files.

  • ADMISAPI:- It contains soap services for Central Administration. If this directory is altered, remote site creation and other methods exposed in the service will not function correctly.
  • Bin:- The directory contains all the core binary files, utilities which used by SharePoint Services.  command line tools such as STSADM.EXE also present in this folder.
  • Client:- This directory contains files that are used for creating office apps.
  • Config:- This directory contains files used to extend IIS Web sites with SharePoint Server. If this directory or its contents are altered, Web application will not function correctly.
  • HCCab:- This directory has a set of cab files which has content information used by the SharePoint help system.
  • Help:- The folder contains html help file (.chm) used by the configuration wizard.
  • ISAPI:- This directory contains all the standard Web Services for SharePoint and resources and configuration files that the web services use.
  • Logs:- This is the folder where we can have all the SharePoint related logs will see. This is important when any problem or error occur in SharePoint you have to trace the logs files in this folder to get the error messages.
  • Policy:- This directory contains SharePoint 2013 Server policy files.
  • Resources:- This directory contains the core.resx file used for creating language packs for SharePoint.   by which different SharePoint sites with different languages and cultures can be create.
  • Template:- It contains the core web site functionality like the features, templates, configurations, resources of a web site.
  • UserCode:- This directory contains files used to support sandbox solution.
  • Web Clients:- This directory contains files related to Client Object Model.
  • Web Services:- This directory is the root directory where SharePoint back-end Web services are hosted, for example, Excel and Search.


Other Important Directories In SharePoint 2013 
1) C:\Inetpub\wwwroot\wss – This directory (or the corresponding directory under the Inetpub root on the server) is used as the default location for IIS Web sites.
2) C:\ProgramFiles\Microsoft Office Servers\15.0 – This directory is the installation location for SharePoint Server 2013 binaries and data. The directory can be changed during installation.
3) C:\ProgramFiles\Microsoft Office Servers\15.0\WebServices – This directory is the root directory where SharePoint back-end Web services are hosted, for example, Excel and Search.
4) C:\ProgramFiles\Microsoft Office Servers\15.0\Data – This directory is the root location where local data is stored, including search indexes.
5) C:\ProgramFiles\Microsoft Office Servers\15.0\Logs – This directory is the location where the run-time diagnostic logging is generated.

___________________________

How to change the deployment location from 14 to 15 hives?

The below figure represents the properties of the package of the solution. You can see that SharePoint Product version in the below figure is set to 15.0, so  that  means the solution will get deployed to 15 hive.

SharePoint product version

Please see the manifest details in below code snippet. I have changed the SharePoint Product version =14.0 so that it can be deployed 14 hive.

SolutionId=“6d5938d4-718c-4557-a8b2-02f2e081390a”
SharePointProductVersion=“14.0”>
<Assemblies>
<Assembly Location=“SharePoint Product Version.dll” DeploymentTarget=“GlobalAssemblyCache”>
<SafeControls>
<SafeControl Assembly=“SharePoint Product Version, Version=1.0.0.0, Culture=neutral, PublicKeyToken=6fb9dacb5ba5cf05” Namespace=“SharePoint_Product_Version.Projects_Webpart” TypeName=“*” />
</SafeControls>
</Assembly>
</Assemblies>
<FeatureManifests>
<FeatureManifest Location=“SharePoint Product Version_14 hive\Feature.xml” />
</FeatureManifests>
</Solution>

SharePoint 2013 /_layouts/15 vs /_layouts folder differences

In SharePoint 2013 it’s possible to install both SharePoint 2010 and 2013 solutions, which is supported by having two folders – one for the Sp2010 (“14″) hive files and one for the SP 2013 (“15″) hive files.

In IIS a virtual directory called 15 now exists in the _layouts folder of the SharePoint web application. If your legacy SharePoint 2010 solution had assets with filepath references, for example,/_layouts/images/test/test.jpg , you would need to update it to /_layouts/15/images/test/test.jpg in order for the path to be resolved correctly when using the solution in SharePoint 2013.

Folder Mappings:

Virtual Directory Folder
_layouts 14/layouts
_layouts/15 15/layouts

Now you have to change the css and all the references if you are deploying your data in to 15 hive instead of 14 hive mapped folder.

We recently encountered a commercial web part where the icons for the web part in the Insert web part ribbon bar area were broken. It turns out the developers must have left the old SharePoint 14 hive reference style in and did not make the distinction so the broken image reference had the path:
https://sitename/_layouts/MyWebPart/Images/PendingMyApproval.png
where it should have actually been:
https:// sitename/_layouts/15/MyWebPart/Images/PendingMyApproval.png

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s