Bolufer Blog - SharePoint & .NET language

The minimum download strategy is a new feature of SharePoint 2013 that reduces the amount of data by downloading only the differences between current page and the requested page. When you enable MDS, you will always load the page from “_layouts/15/start.aspx” followed by a hash(#) and then the relative url of the site you requested. Example: http://<your site url>/_layouts/15/start.aspx#/SitePages/test.aspx If MDS is disabled, the above page URL will be http://sp_site/SitePages/test.aspx Enable MDS through Site Settings You can enable or disable MDS by visiting the Site Features page and activating / deactivating the feature. Go to your site settings page for the site you need to enable or disable the feature. Under Site actions you can find Manage site features. In the site features page, you can see whether the feature is active or not. You can use the Activate/Deactivate button to enable or disable the Minimal download strategy for your site. En

SharePoint 2013 have out of the box support for publishing RSS feed for lists and libraries.  For publishing portals it is important to expose the site contents as RSS feeds. In this walkthrough I am going to explain how you can configure RSS feed for lists, libraries etc. in the SharePoint portal with your own display. For the purpose of this walkthrough, I have created a picture Library named “MyPictures” and added five pictures to this library. The thumbnail view of the picture library is as follows. Now go to the library tab of your list page. You can see the RSS feed icon is disabled, this is because I didn’t enable the RSS feed for my site. Now let us see how we can enable the RSS feed settings. Enable RSS feed for Sites/Site Collection Initially you need to enable the RSS feed for the site collection and the site where you need to expose your contents as RSS feeds. Go to your top level site settings page, if you are in a sub site, make sure you click

Recently in one of my project, I wanted to retrieve the logged in user’s login name in the format of domain\username. This seems simple and to retrieve the username, I used the below code. SPContext.Current.Web.CurrentUser.LoginName But the output I received contains some extra stuff along with my domain name and username. My domain name is sp1013domain and user name is spsetup, see the output that generated by the above line of code. i:0#.w|sp2013domain\spsetup While searching over web, I found some guys speaking about retrieving the domain\username by splitting the above result by pipe (|) symbol, I was not convinced with that. The extra characters added to the login name is by the claims authentication, so definitely we should be able to retrieve it automated. There is a SPClaimProviderManager class that is responsible for management of various claim providers in the SharePoint farm, and there is a DecodeClaim method, that decodes a claim from an encoded string,

Recently I came across a requirement in one of the SharePoint 2013 on premise portal implementation. All the user’s picture is updated in active directory, the question was can we import this picture uploaded to active directory to the Picture property in user profile. The answer is yes and in this post I am explaining the steps for doing it so. So first thing I wanted to do in my development environment to update the photo in the active directory. It can be done by PowerShell script, but I found a nice that can do this task and thankfully there is a free version available. You can find the tool from the below link. http://www.cjwdev.co.uk/Software/ADPhotoEdit/Info.html I downloaded the tool and installed on my development environment. Uploading profile picture with the tool is easy and straight forward, just select the user account and then select an image. For the purpose of this post, I uploaded a sample picture for the account “SPSetup”. The belo

In SharePoint there will be times where you will want to control what results the people picker returns. The most common scenarios are in an extranet or hosting environment. There are four strategies which can be used to limit the people picker. All of these are managed using STSADM commands. The four strategies are:- Applying a custom active directory filter Limiting the people picker search to within a site collection Limiting the people picker search to within an Active Directory(AD) Organisational Unit(OU) Disable returning windows accounts when the authentication method for the web application is via forms based authentication Some of these commands are not very well known and some are new in MOSS SP1. Custom Active Directory Filter To limit the search to a custom AD filter use the STSADM property peoplepicker-searchadcustomfilter This property is new in SP1 and when a people search is executed it will return results that only match the combination of the buil

Language - Country/Region LCID Hex LCID Dec Afrikaans - South Africa 0436 1078 Albanian - Albania 041c 1052 Alsatian 0484 1156 Amharic - Ethiopia 045e 1118 Arabic - Saudi Arabia 0401 1025 Arabic - Algeria 1401 5121 Arabic - Bahrain 3c01 15361 Arabic - Egypt 0c01 3073 Arabic - Iraq 0801 2049 Arabic - Jordan 2c01 11265 Arabic - Kuwait 3401 13313 Arabic - Lebanon 3001 12289 Arabic - Libya 1001 4097 Arabic - Morocco 1801 6145 Arabic - Oman 2001 8193 Arabic - Qatar 4001 16385 Arabic - Syria 2801 10241 Arabic - Tunisia 1c01 7169 Arabic - U.A.E. 3801 14337 Arabic - Yemen 2401 9217 Armenian - Armenia 042b 1067 Assamese 044d 1101 Azeri (Cyrillic) 082c 2092 Azeri (Latin) 042c 1068 Bashkir 046d 1133 Basque 042d 1069 Belarusian 0423 1059 Bengali (India) 0445 1093 Bengali (Bangladesh) 0845 2117 Bosnian (Bosnia/Herzegovina) 141A 5146 Breton 047e 1150 Bulgarian 0402 1026 Burmese 0455 1109 Catalan 0403 1027 Cherokee - United States 045c 1116 Chinese - People's