Microsoft.sharepoint.library version=15.0.0.0 download

Introduction

In a recent project I was asked to consult in, the team needed to create sub site/s for news or events.

Developing for re-usability in SharePoint is something I find is lacking quite a bit in Development teams.

Below I outline the solution I worked out for the project, that is also now a template that the Team can use in any similiar project.

I will explain not only how to do it step by step but also continue to make this page layout as the default page layout of a publishing sub site.

After that, make a content query in the root site to preview the news articles.

Finally, I will be using variation to create a similar publishing sub site in other languages.

1. Step by step creation of News Page Layout using Content Type in SharePoint 2013.
2. How to Create a publishing sub site for news and using variation to creating the same site to other languages finally making the previous page layout as the default page layout of the sub site.

Firstly

1. Open Visual Studio 2013 and a create new project of type SharePoint Solutions…”SharePoint 2013 Empty Project”.
   Create new SharePoint 2013 empty project
2. As we will deploy our solution as a farm solution in our local farm on our local machine.
   Note: Make sure that the site is a publishing site to be able to proceed.
   Deploy the SharePoint site as a farm solution
3. Our solution will be as the picture blew and we will add three folders for “SiteColumns”, “ContentTypes” and “PageLayouts”.
   SharePoint solution items
4. Start by adding a new item to “SiteColumns” folder.
   Adding new item to SharePoint solution
5. After we adding a new site column and rename it, add the following columns as we need to make the news layout , , , and .
   Adding new item of type site column to the solution

   Then add the below fields and you will note that I use in the and the .

   Collapse | Copy Code
   <FieldID="{9fd593c1-75d6-4c23-8ce1-4e5de0d97545}"Name="NewsTitle"DisplayName="$Resources:SPWorld_News,NewsTitle;"Type="Text"Required="TRUE"Group="$Resources:SPWorld_News,NewsGroup;"></Field><FieldID="{fcd9f32e-e2e0-4d00-8793-cfd2abf8ef4d}"Name="NewsBrief"DisplayName="$Resources:SPWorld_News,NewsBrief;"Type="Note"Required="FALSE"Group="$Resources:SPWorld_News,NewsGroup;"></Field><FieldID="{FF268335-35E7-4306-B60F-E3666E5DDC07}"Name="NewsBody"DisplayName="$Resources:SPWorld_News,NewsBody;"Type="HTML"Required="TRUE"RichText="TRUE"RichTextMode="FullHtml"Group="$Resources:SPWorld_News,NewsGroup;"></Field><FieldID="{FCA0BBA0-870C-4D42-A34A-41A69749F963}"Name="NewsDate"DisplayName="$Resources:SPWorld_News,NewsDate;"Type="DateTime"Required="TRUE"Group="$Resources:SPWorld_News,NewsGroup;"></Field><FieldID="{8218A8D9-912C-47E7-AAD2-12AA10B42BE3}"Name="NewsImage"DisplayName="$Resources:SPWorld_News,NewsImage;"Required="FALSE"Type="Image"RichText="TRUE"RichTextMode="ThemeHtml"Group="$Resources:SPWorld_News,NewsGroup;"></Field>

   After That

6. Create Content Type, we will be adding new Content Type to the folder ContentTypes.
   Adding new item of type Content Type to SharePoint solution
7. We must make sure to select the base of the content type “”.
   Specifying the base type of the content type
8. Open the content type and add our new columns to it.
   Adding columns to the content type
9. Open the elements file of the content type and make sure it will look like this code below.Note: We use in the , and the group of the content type. <!-- Parent ContentType: Page (0x010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130EC3DB064584E219954237AF39) --><ContentTypeID="0x010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130EC3DB064584E219954237AF39007A5224C9C2804A46B028C4F78283A2CB"Name="$Resources:SPWorld_News,NewsContentType;"Group="$Resources:SPWorld_News,NewsGroup;"Description="$Resources:SPWorld_News,NewsContentTypeDesc;"Inherits="TRUE"Version="0"><FieldRefs><FieldRefID="{9fd593c1-75d6-4c23-8ce1-4e5de0d97545}"DisplayName="$Resources:SPWorld_News,NewsTitle;"Required="TRUE"Name="NewsTitle"/><FieldRefID="{fcd9f32e-e2e0-4d00-8793-cfd2abf8ef4d}"DisplayName="$Resources:SPWorld_News,NewsBrief;"Required="FALSE"Name="NewsBrief"/><FieldRefID="{FF268335-35E7-4306-B60F-E3666E5DDC07}"DisplayName="$Resources:SPWorld_News,NewsBody;"Required="TRUE"Name="NewsBody"/><FieldRefID="{FCA0BBA0-870C-4D42-A34A-41A69749F963}"DisplayName="$Resources:SPWorld_News,NewsDate;"Required="TRUE"Name="NewsDate"/><FieldRefID="{8218A8D9-912C-47E7-AAD2-12AA10B42BE3}"DisplayName="$Resources:SPWorld_News,NewsImage;"Required="FALSE"Name="NewsImage"/></FieldRefs></ContentType>
10. Add new Module to the PageLayouts folder. After that, we will find sample.txt file, then rename it “NewsPageLayout.aspx”.
    Adding new module to SharePoint solution.
11. Add the code below to this “NewsPageLayout.aspx”. <%@ Page language="C#" Inherits="Microsoft.SharePoint.Publishing.PublishingLayoutPage, Microsoft.SharePoint.Publishing,Version=15.0.0.0,Culture=neutral,PublicKeyToken=71e9bce111e9429c"%><%@ Register Tagprefix="SharePointWebControls" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"%><%@ Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"%><%@ Register Tagprefix="PublishingWebControls" Namespace="Microsoft.SharePoint.Publishing.WebControls" Assembly="Microsoft.SharePoint.Publishing, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"%><%@ Register Tagprefix="PublishingNavigation" Namespace="Microsoft.SharePoint.Publishing.Navigation" Assembly="Microsoft.SharePoint.Publishing, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"%><asp:ContentContentPlaceholderID="PlaceHolderPageTitle"runat="server"><SharePointWebControls:FieldValueid="FieldValue1"FieldName="Title"runat="server"/></asp:Content><asp:ContentContentPlaceholderID="PlaceHolderMain"runat="server"><H1><SharePointWebControls:TextFieldID="NewsTitle"FieldName="9fd593c1-75d6-4c23-8ce1-4e5de0d97545"runat="server"></SharePointWebControls:TextField></H1><p><PublishingWebControls:RichHtmlFieldID="NewsBody"FieldName="FF268335-35E7-4306-B60F-E3666E5DDC07"runat="server"></PublishingWebControls:RichHtmlField></p><p><SharePointWebControls:NoteFieldID="NewsBrief"FieldName="fcd9f32e-e2e0-4d00-8793-cfd2abf8ef4d"runat="server"></SharePointWebControls:NoteField></p><p><SharePointWebControls:DateTimeFieldID="NewsDate"FieldName="FCA0BBA0-870C-4D42-A34A-41A69749F963"runat="server"></SharePointWebControls:DateTimeField></p><p><PublishingWebControls:RichImageFieldID="NewsImage"FieldName="8218A8D9-912C-47E7-AAD2-12AA10B42BE3"runat="server"></PublishingWebControls:RichImageField></p></asp:Content>
12. Add the following code to the elements file of the “” module. <ModuleName="NewsPageLayout"Url="_catalogs/masterpage"List="116"><FilePath="NewsPageLayout\NewsPageLayout.aspx"Url="NewsPageLayout.aspx"Type="GhostableInLibrary"IgnoreIfAlreadyExists="TRUE"ReplaceContent="TRUE"Level="Published"><PropertyName="Title"Value="$Resources:SPWorld_News,NewsPageLayout;"/><PropertyName="MasterPageDescription"Value="$Resources:SPWorld_News,NewsPageLayout;"/><PropertyName="ContentType"Value="$Resources:cmscore,contenttype_pagelayout_name;"/><PropertyName="PublishingPreviewImage"Value="~SiteCollection/_catalogs/masterpage/$Resources:core,Culture; /Preview Images/WelcomeSplash.png, ~SiteCollection/_catalogs/masterpage/$Resources: core,Culture;/Preview Images/WelcomeSplash.png"/><PropertyName="PublishingAssociatedContentType"Value=";#$Resources:SPWorld_News,NewsContentType;; #0x010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130EC3DB064584E219954237AF39007A5224C9C2804A46B028C4F78283A2CB;#"></Property></File></Module>
13. Don’t forget to add the Resources folder, then add the resource file with the name “SPWorld_News.resx” as we used it in the previous steps and add the below keys to it. News News NewsBody News Body NewsBrief News Brief NewsContentType News Content Type NewsContentTypeDesc News Content Type Desc. NewsDate News Date NewsGroup News NewsImage News Image NewsPageLayout News Page Layout NewsTitle News Title
14. Finally, deploy the solution.
15. The next steps will explain how we add the “news content type” to the page layout through SharePoint wizard. We will do these steps pragmatically in the next article.Note: We will do the steps from “A” to “D” pragmatically in the next article without the need to do it manually from SharePoint.

    

    1. Go to Site Contents then Pages , Library, Library SettingsOpening library setting of the page library
    2. Add the news content type to the page layout.
       Adding existing content type to the pages library
    3. Then
       Selecting the content type to add it to pages library
    4. Go to Pages Library, Files, New Document, select News Content Type.
       Adding new document of the news content type to pages library
    5. Write the page title.
       Creating new page of news content type to pages library.
    6. Open the page to edit it. Pages library contains new page of news content type.
    7. Now we can see the page Layout after we add the title, Body, Brief, date and image. Finally click Save the news.

While everyone is talking about Apps, there are still significant investments in Full Trust Solutions (a.k.a. Farm Solutions) and I am sure that many OnPrem deployments will want to carry these forward when upgrading to SharePoint 2013.  The new SharePoint 2013 upgrade model allows Sites to continue to run in 2010 mode after upgrading and each Site Collection explicitly has to be upgraded individually.

Not the way it worked in 2010 with Visual Upgrade, but this time there is actually both a 14 and 15 Root folder deployed and all the Features and Layout files from SharePoint 2010 are deployed as part of the 2013 installation.

For those of you new to SharePoint, the root folder is where SharePoint keeps most of its application files and the default location for this is “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\[SharePoint Internal Version]”, where the versions for the last releases have been 60 (6.0), 12, 14, and now 15. The location is also known as “The xx hive.”

This is great in an upgrade scenario, where you may want to do a platform upgrade first or only want to share the new features of 2013 with a few users while maintaining an unchanged experience for the rest of the organization.  This also gives us the opportunity to have different functionality and features for sites running in 2010 and 2013 mode.  However, this requires some extra thought in the development and deployment process that I will give an introduction to here.

Because you can now have Sites running in both 2010 and 2013 mode, SharePoint 2013 introduces a new concept of a Compatibility Level.  Right now it can only be 14 or 15, but you can imagine that there is room for growth.  This Compatibility Level is available at Site Collection and Site (web) level and can be used in code constructs and PowerShell commands.  I will start by explaining how you use it while building and deploying wsp-files for SharePoint 2013 and then finish off with a few things to watch out for and some code tips.

Deployment Considerations

If you take your wsp-files from SharePoint 2010 and just deploy these with Add-SPSolution -> Install-SPSolution as you did in 2010, then SharePoint will assume it is a 2010 solution or a “14” mode solution.  If the level is not specified in the PowerShell command, it determines the level based on the value of the SharePointProductVersion attribute in the Solution manifest file of the wsp-package.  The value can currently be 15.0 or 14.0. If this attribute is missing, it will assume 14.0 (SharePoint 2010) and since this attribute did not exist in 2010, only very well informed people will have this included in existing packages.

For PowerShell cmdlets related to installing solutions and features, there is a new parameter called CompatibilityLevel. This can override the settings of the package itself and can assume the following values: 14, 15, New, Old, All and “14,15” (the latter currently also means All).

The parameter is available for Install-SPSolution, Uninstall-SPSolution, Install-SPFeature and Uninstall-SPFeature.  There is no way to specify “All” versions in the package itself – only the intended target – and therefore these parameters need to be specified if you want to deploy to both targets.

It is important to note that Compatibility Level impacts only files deployed to the Templates folder in the 14/15 Root folder. That is:  Features, Layouts-files, Images, ControlTemplates, etc.

This means that files outside of this folder (e.g. a WCF Service deployed to the ISAPI folder) will be deployed to the 15/ISAPI no matter what level is set in the manifest or PowerShell.  Files such as Assemblies in GAC/Bin and certain resource files will also be deployed to the same location regardless of the Compatibility Level.

It is possible to install the same solution in both 14 and 15 mode, but only if it is done in the same command – specifying Compatibility Level as either “All” or “14,15”.  If it is first deployed with 14 and then with 15, it will throw an exception.  It can be installed with the –Force parameter, but this is not recommended as it could hide other errors and lead to an unknown state for the system.

The following three diagrams illustrate where files go depending on parameters and attributes set (click on the individual images for a larger view). Thanks to the Ignite Team for creating these. I did some small changes from the originals to emphasize a few points.

When retracting the solutions, there is also an option to specify Compatibility Level.  If you do not specify this, it will retract all – both 14 and 15 files if installed.  When deployed to both levels, you can retract one, but the really important thing to understand here is that it will not only retract the files from the version folder, but also all version neutral files – such as Assemblies, ISAPI deployed files, etc. – leaving only the files from the Root folder you did not retract.

To plan for this, my suggestion would be the following during development/deployment:

• If you want to only run sites in 2013 mode, then deploy the Solutions with CompatibilityLevel 15 or SharePointProductVersion 15.0.
• If you want to run with both 2010 and 2013 mode, and want to share features and layout files, then deploy to both (All or “14,15”).
• If you want to differentiate the files and features that are used in 2010 and 2013 mode, then the solutions should be split into two or three solutions:
  • One solution (“Xxx – SP2010”), which contains the files and features to be deployed to the 14 folder for 2010 mode.  including code-behind (for things like feature activation and Application pages), but excluding shared assemblies and files.
  • One solution (“Xxx – SP2013”), which contains the files and features to be deployed to the 15 folder for 2013 mode, including code-behind (for things like feature activation and Application pages), but excluding shared assemblies and files.
  • One solution (“Xxx – Common”), which contains shared files (e.g. common assemblies or web services). This solution would also include all WebApplication scoped features such as bin-deployed assemblies and assemblies with SafeControl entries.
• If you only want to have two solutions for various reasons, the Common solution can be joined with the SP2013 solution as this is likely to be the one you will keep the longest.
• The assemblies being used as code-files for the artifacts in SP2010 and SP2013 need to have different names or at least different versions to differentiate them. Web Parts need to go in the Common package and should be shared across the versions, however the installed Web Part templates can be unique to the version mode.

Things to watch out for…

There are a few issues that are worth being aware of that may be fixed in future updates, but you’ll need to watch out for these currently.  I’ve come across an issue where installing the same solution in both levels can go wrong.  If you install it with level All and then uninstall it with level 14 two times, the deployment logic will think that it completely removed the solution, but the files in the 15/Templates folder will still be there.

To recover from this, you can install it with –Force in the orphan level and then uninstall it.  Again, it is better to not get in this situation.

Another scenario that can get you in trouble is if you install a solution in one Compatibility Level (either through PowerShell Parameter or manifest file attribute) and then uninstall with the other level.  It will then remove the common files but leave the specific 14 or 15 folder files and display the solution as fully retracted.

Unfortunately there is no public API to query which Compatibility Levels a package is deployed to.  So you need to get it right the first time or as quickly as possible move to native 2013 mode and packages (this is where we all want to be anyway).

Code patterns

An additional tip is to look for hard coded paths in you custom code such as _layouts and _controltemplates.  The SPUtility class has been updated with static methods to help you parse the current location based on the upgrade status of the Site.   For example, SPUtility.ContextLayoutsFolder will give you the path to the correct layouts folder.  See the reference article on SPUtility properties for more examples.

Round up

I hope this gave you an insight into some of the things you need to consider when deploying Farm Solutions for SharePoint 2013. There are lots of scenarios that are not covered here. If you find some, please share these or share your concerns and I will try to add it as comments or an additional post.

This is a simple, C# class library project to connect .NET applications with SAP.

This component internally implements SAP .NET Connector 3.0. The SAP .NET Connector is a development environment that enables communication between the Microsoft .NET platform and SAP systems.

This connector supports RFCs and Web services, and allows you to write different applications such as Web form, Windows form, or console applications in the Microsoft Visual Studio .NET.

With the SAP .NET Connector, you can use all common programming languages, such as Visual Basic. NET, C#, or Managed C++.

Features
Using the SAP .NET Connector you can:

Write .NET Windows and Web form applications that have access to SAP business objects (BAPIs).

Develop client applications for the SAP Server.

Write RFC server applications that run in a .NET environment and can be installed starting from the SAP system.

Following are the steps to configure this utility on your project

Download and extract the attached file and place it on your machine. This package contains 3 libraries:

SAPConnectionManager.dll
sapnco.dll
sapnco_utils.dll

Now go to your project and add the reference of all these four libraries. Sapnco.dll and sapnco_utils.dll are inbuilt libraries used by SAP .NET Connector. SAPConnectionManager.dll is the main component which provides the connection between .NET and SAP.

Once the above steps are complete, you need to make certain entries related to SAP server on your configuration file. Here are the sample entries that you have to maintain on your own project. You need to change only the values which are marked in Bold. Rest remains unchanged.

<appSettings>
<add key=”ServerHost” value=”127.0.0.1″/>
<add key=”SystemNumber” value=”00″/>
<add key=”User” value=”sample”/>
<add key=”Password” value=”pass”/>
<add key=”Client” value=”50″/>
<add key=”Language” value=”EN”/>
<add key=”PoolSize” value=”5″/>
<add key=”PeakConnectionsLimit” value=”10″/>
<add key=”IdleTimeout” value=”600″/>
</appSettings>

To test this component, create one windows application. Add the reference of sapnco.dll, sapnco_utils.dll, andSAPConnectionManager.dll on your project.

Paste the below code on your Form lode event

SAPSystemConnect sapCfg = new SAPSystemConnect();
RfcDestinationManager.RegisterDestinationConfiguration(sapCfg);
RfcDestination rfcDest = null;
rfcDest = RfcDestinationManager.GetDestination(“Dev”);

That’s it. Now you are successfully connected with your SAP Server. Next you need to call SAP business objects (BAPIs) and extract the data and stored it in DataSet or list.

Demo Code available on request!!

Cross-site publishing is one of the powerful new capabilities in SharePoint 2013.  It enables the separation of data entry from display and breaks down the container barriers that have traditionally existed in SharePoint (ex: rolling up information across site collections). 

Cross-site publishing is delivered through search and a number of new features, including list/library catalogs, catalog connections, and the content search web part.  Unfortunately, SharePoint Online/Office 365 doesn’t currently support these features.  Until they are added to the service (possibly in a quarterly update), customers will be looking for alternatives to close the gap.  In this post, I will outline several alternatives for delivering cross-site and search-driven content in SharePoint Online and how to template these views for reuse

The new SharePoint app model is fully supported in SharePoint Online and can be used to deliver customizations to SharePoint using any web technology.  New SharePoint APIs can be used with the app model to deliver an experience similar to cross-site publishing.  In fact, the content search web part could be re-written for delivery through the app model as an “App Part” for SharePoint Online. 
Although the app model provides great flexibility and reuse, it does come with some drawbacks.  Because an app part is delivered through a glorified IFRAME, it would be challenging to navigate to a new page from within the app part.  A link within the app would only navigate within the IFRAME (not the parent of the IFRAME).  Secondly, there isn’t a great mechanism for templating a site to automatically leverage an app part on its page(s).  Apps do not work with site templates, so a site that contains an app cannot be saved as a template.  Apps can be “stapled” to sites, but the app installed event (which would be needed to add the app part to a page) only fires when the app is installed into the app catalog.

The script editor web part is a powerful new tool that can help deliver flexible customization into SharePoint Online.  The script editor web part allows a block of client-side script to be added to any wiki or web part page in a site.  Combined with the new SharePoint REST APIs, the script editor web part can deliver mash-ups very similar to cross-site publishing and the content search web part.  Unlike apps for SharePoint, the script editor isn’t constrained by IFRAME containers, app permissions, or templating limitations.  In fact, a well-configured script editor web part could be exported and re-imported into the web part gallery for reuse.

Cross-site publishing leverages “catalogs” for precise querying of specific content.  Any List/Library can be designated as a catalog.  By making this designation, SharePoint will automatically create managed properties for columns of the List/Library and ultimately generate a search result source in sites that consume the catalog.  Although SharePoint Online doesn’t support catalogs, it support the building blocks such as managed properties and result sources.  These can be manually configured to provide the same precise querying in SharePoint Online and exploited in the script editor web part for display.

An easier approach might be to directly reference a list/library in the REST call of our client-side script.  This wouldn’t require manual search configuration and would provide real-time publishing (no waiting for new items to get indexed).  You could think of this approach similar to a content by query web part across site collections (possibly even farms) and the REST API makes it all possible!

The content search web part uses display templates to render search results in different arrangements (ex: list with images, image carousel, etc).  There are two types of display templates the content search web part leverages…the control template, which renders the container around the items, and the item template, which renders each individual item in the search results.  This is very similar to the way a Repeater control works in ASP.NET.  Display templates are authored using HTML, but are converted to client-side script automatically by SharePoint for rendering.  I mention this because our approach is very similar…we will leverage a container and then loop through and render items in script.  In fact, all the examples in this post were converted from display templates in a public site I’m working on. 

Even one of the more complex carousel views from my site took less than 30min to convert to the script editor approach.