Deploying File Along With Feature

Few days back, I was working to create an Editor Web Part. The Editor Part contains a drop down and I need to populate it with an XML file (Links.xml) . I had given the file name in XmlDatasource, considering it would be picked, but Editor part gave me an error i.e. file not found.

After doing some research, I came to know a new deployment type ElementFile. This deployment type physically deploy the file along with the feature and we can get the path of the feature then.

SharePoint provides a method for this purpose i.e.. SPUtility.GetGenericSetupPath. By using this method I found my XML file and me editor part started working. I hope this will help any other newbie  in SharePoint..... :)fF

14 HIVE AND OTHER SHAREPOINT 2010 DIRECTORIES

In this post I will list out some important folders used with SharePoint 2010 server. Lets Start with  installation, Configuration and its files, later in the post we will discuss about other 14 hive directories.

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.

C:\ProgramFiles\Microsoft Office Servers\14.0 - This directory is the installation location for SharePoint Server 2010 binaries and data. The directory can be changed during installation.

C:\ProgramFiles\Microsoft Office Servers\14.0\WebServices - This directory is the root directory where SharePoint back-end Web services are hosted, for example, Excel and Search.

C:\ProgramFiles\Microsoft Office Servers\14.0\Data - This directory is the root location where local data is stored, including search indexes.

C:\ProgramFiles\Microsoft Office Servers\14.0\Logs – This directory is the location where the run-time diagnostic logging is generated.

14 hive folders : 

Program Files\Common files\Microsoft Shared\Web Server Extensions\14 -
This directory is the installation directory for core SharePoint Server files.

Program Files\Common files\Microsoft Shared\Web Server Extensions\14\ADMISAPI -
This directory contains the soap services for Central Administration. If this directory is altered, remote site creation and other methods exposed in the service will not function correctly.

Program Files\Common files\Microsoft Shared\Web Server Extensions\14\CONFIG -
This directory contains files used to extend IIS Web sites with SharePoint Server. If this directory or its contents are altered, Web application provisioning will not function correctly.

Program Files\Common files\Microsoft Shared\Web Server Extensions\14\LOGS -
This directory contains setup and run-time tracing logs.

Program Files\Common files\Microsoft Shared\Web Server Extensions\Policy -

Program Files\Common files\Microsoft Shared\Web Server Extensions\UserCode -
This directory contains files used to support your sandboxed solutions.

Program Files\Common files\Microsoft Shared\Web Server Extensions\WebClients -
This directory contains files related to the new Client Object Model.

Program Files\Common files\Microsoft Shared\Web Server Extensions\WebServices -
This directory contains new wcf or .svc related files.

I hope this post will be helpful for you in understanding SharePoint 14  Hive folder hierarchy. Thank You,.

SharePoint Hives Folders

SharePoint has hives folder for all the SharePoint major versions i.e 2007 has 12 hive, 2010 has 14 hive and now SharePoint 2013 has 15 hive folder. Let me elaborate the naming convention that why SharePoint has different hives folder name, then the SharePoint release name.

Basically Hive folder naming convention is development version of SharePoint. As SharePoint team is keep on working on different features of SharePoint all the team, so keep on creating different versions but Hive represent the production version which Microsoft release for SharePoint  I hope this post will help you in understanding why we have different Hive folder naming convention, then SharePoint.

Thank You.

Comments Rendering Issue in Sharepoint

I was working on a custom SharePoint master page, few days ago. After deploying the master page in Gallery, I set it for my site-collection. I had started facing a strange error i..e master tag is already defined. Initially I thought, that SharePoint existing pages, inherited from some other master page and I might override  it, but it also didn't work.

After some time, I started looking my master page html, I had a commented master tag, which I believe should not be rendered by SharePoint, as commented. I removed the commented tag for testing purpose, and surprisingly things starts working. SharePoint engine actually render the commented tag as well.

I hope this post will help any newbie in SharePoint world..... Happy Coding.....:)

Generating Public key token

Many times we need to get the Public key token for a strongly named assembly in .NET.  “how to get the public key token?”. Answer is very simple use the .NET Framework tools sn.exe. So open the Visual Studio 2008 Command Prompt and then point to the dll’s folder you want to get the public key,

I have used the following command, for generating public key token for a SharePoint project

sn.exe –T SPExcercise1.dll

Public key token is d95388ccbe5ad4c1

This will give you the public key token. 

Remember one thing this only works if the assembly has to be strongly signed.

soap:ServerServer was unable to process request. ---> Value does not fall within the expected range.

In some odd situation, SharePoint Designer (SPD) 2010 would throw this error:

“soap:Server was unable to process request. Value does not fall within the expected range”

Cause
SPD does not open the site with name it was originally defined.  For example, the site was created as http://xyzmachine:9999/, but SPD connects it as http://localhost:9999/

Solution
SPD should connect the site with name/url defined at its creation.