General Repro Steps –

1. For every first XMLHttpRequest, a keep alive connection (TCP Connection) is created which is used by any subsequent request. If the connection is forcibly closed by the browser, then browsers will try to create a new connection by resubmitting the request.
2. For GET Requests it will work without any issues. But for POST it will only send Request Headers and not the body in Internet Explorer. That’s why you will receive error – The request body did not contain the specified number of bytes. Got 0, expected xxx.
3. As a solution either install above mentioned Hotfix or Use NEW unique URL by adding TimeStamp to URL to avoid any re-POST request.

For e.g.

var urlToPost = "ajaxUrlToPost.svc?stamp=' + new Date().getTime();

The post The request body did not contain the specified number of bytes. Got 0, expected xxx – Internet Explorer Issue appeared first on Pritam's Blog.

Time Zone plays very crucial roles in any Date Time difference calculation. When we do difference in two date times, it must be in same Time Zone offset otherwise the result will never be correct. Here, TimeZoneInfo class plays main role. To get specific time zone details we have to use TimeZoneInfo.FindSystemTimeZoneById method which will take input of Zone Id. All available Time Zone Id’s can be found at MSDN https://msdn.microsoft.com/en-us/library/gg154758.aspx.

To explain this problem lets take a example that we need to find all SharePoint List items which was created in last 5 minutes.

First we will retrieve all Items from a List which is created Today. We will use CAML Query to get these items.

// Store result in temporary Table
DataTable dataResult = new DataTable();
dataResult.Columns.Add("ID");
dataResult.Columns.Add("Title");

//Get List Data
SPWeb sbWeb = SPContext.Current.Site.RootWeb;
SPList list = sbWeb.GetList("MyCustomList");
SPQuery listQuery = new SPQuery();

// Get items for todays date
listQuery.Query = "<Where><Eq><FieldRef Name='Created' /><Value Type='DateTime'><Today /></Value></Eq></Where>";
SPListItemCollection items = list.GetItems(listQuery);

Iterate through each list item and perform Date time conversion.

foreach(SPListItem item in items) {
	if (item[“Title”] != null && item[“ID”] != null) {

		// Get UTC Now Date Time
		DateTime utcNowDate = new DateTime(DateTime.UtcNow.Ticks, DateTimeKind.Utc);

		// Find the Server Time Zone Info which is configured under Central Administration -> Web Application -> General Settings
		TimeZoneInfo timeZoneInfo = TimeZoneInfo.FindSystemTimeZoneById(“Pacific Standard Time”);

		// Convert UTC Now Date Time to server’s Time Zone i.e. into Pacific Standard Time in our example.
		DateTime convertedUtcNowDateTime = TimeZoneInfo.ConvertTimeFromUtc(utcNowDate, timeZoneInfo);

		// Find the Date time difference into TimeSpan
		TimeSpan diffResult = convertedUtcNowDateTime–Convert.ToDateTime(item[“Created”]);

		// Create 5 Minutes Time Span object
		TimeSpan fiveMinutesSpan = new TimeSpan(0, 5, 0);

		// Compare method will return -1 if first time interval is shorter than second and return 0 if both time interval are equal. Read more about this at https://msdn.microsoft.com/en-us/library/system.timespan.compare(v=vs.110).aspx
		int result = TimeSpan.Compare(diffResult, fiveMinutesSpan);

		// If result is 0 Or -1 it means items is created in last five minutes.
		if (a < 1) {
			DataRow row = dataResult.NewRow();
			row["Title"] = item[SPBuiltInFieldId.EncodedAbsUrl].ToString();
			row["ID"] = item[ColumnName.ReportUrl].ToString();
			data.Rows.Add(dr);
		}
	}
}

Resulting DataTable will have the filtered result.

The post SharePoint 2010/2013 Date Comparison in different Time Zones appeared first on Pritam's Blog.

Implementing client side localization into any web application is always challenge. Most of web technologies provide localization using server-side technologies. For e.g. .Net application uses Resources Files(.resx) to implement localization into globalization application.

Nowadays world is extensively moving towards Asynchronous development models like AJAX / SPA. Several frameworks, libraries are already available on the web. To access these server side resources requires custom REST services / handlers to be additionally implemented into the host application.

This plugin makes life easier where you can manage all your localized resources into plain Text or JavaScript file. Based on current culture provided to this plugin, it loads associated resource entries for use. To enhance performance it Cache data for subsequent Initialization calls. So now no more server side development required for managing localization. It can be used in any web applications like SharePoint On-Premise / Online, Php, ASP.Net MVC, JAVA and many more as long as these technologies supports JavaScript.

Download Pugin from Github Github.

Install via Nuget Package.

The post jQuery based Resource Localization appeared first on Pritam's Blog.

To solve this problem, I have created small jQuery plugin which will give you this information at one place. You can search for Culture information by LCID (for e.g. 1033) or by Culture Name (for e.g. en-US), which will return you JSON Object. This plugin can be used in any of your favorite application which supports JavaScript.

1. Refer to the Github Project JQuery Culture Information Plugin
2. Install via the NuGet Package Install-Package PritamBaldota.JqueryCultureInfo

Sharing is Caring

The post JQuery Culture Information Plugin appeared first on Pritam's Blog.

To add content type follow below steps –

• Get Reference to Site collection and root web to get the content types.

[shell]

$siteRef = Get-SPSite http://domain/site
$rootWebRef = $siteRef.RootWeb

[/shell]

• Get the target web reference to which content type will be added for List/Library.

[shell]
$web = Get-SPWeb http://domain/site/web
[/shell]

• Get the reference to target list / library

[shell]
$listRef = $web.Lists[“List Title”]
[/shell]

• Enable the management of content type for this list/library.

[shell]

$listRef.ContentTypesEnabled  = $true
$listRef.Update()

[/shell]

• Get the deployed Content Type reference from root web which will be added to the target list.

[shell]
$targetContentType= $rootWebRef.ContentTypes[“CustomContentType”]
[/shell]

• Check if Content is already exists from ContentTypes collection of a List. If not found then add the content type to the list.

[shell]
$contentTypeExist = $listRef.ContentTypes[$contentType.Name]
if($contentTypeExist -ne $null)
{
$listRef.ContentTypes.Add($targetContentType)
$listRef.Update()
}
[/shell]

To delete content type follow below steps –

To delete content type association from list, we have to get the reference of associated content type and pass the Id of content type to Delete method on ContentTypes collection.

[shell]

$contentTypeExist = $listRef.ContentTypes[$contentType.Name]

$listRef.ContentTypes.Delete($contentTypeExist.Id)

[/shell]

This is how the complete code will look like –

[shell]

$siteRef = Get-SPSite http://domain/site
$rootWebRef = $siteRef.RootWeb
$web = Get-SPWeb http://domain/site/web

$listRef = $web.Lists[“List Title”]
if ($listRef -ne $null)
{
$listRef.ContentTypesEnabled  = $true
$listRef.Update()
$targetContentType = $rootWebRef.ContentTypes[$contentType.Name]
if($targetContentType -ne $null)
{
$contentTypeExist = $listRef.ContentTypes[$contentType.Name]
if($contentTypeExist -ne $null)
{
Write-Host “Adding Content Type – ” $targetContentType.Name -ForegroundColor Green
$listRef.ContentTypes.Add($targetContentType)
}
else
{
Write-Host ”  Content Type already exists – ” $targetContentType.Name -ForegroundColor Green
}
}
$listRef.Update()
}

[/shell]

Happy Coding

The post Associate Custom Content Type with SharePoint 2010/2013 List Or Library using PowerShell appeared first on Pritam's Blog.

• SharePoint Features is part of Packaging and Deployment in SharePoint 2010
• Features make it easier to activate or deactivate functionality in the course of a deployment, and administrators can easily transform the template or definition of a site by simply toggling a particular Feature on or off in the user interface.
• Features are stored under %ProgramFiles%\Common Files\Microsoft Shared\web server extensions\14\TEMPLATE\FEATURES
• The Feature subfolder includes a Feature.xml file and any number of supporting element files.
• Features can be installed/uninstalled using STSADM tool, SharePoint Management Shell, Or Object Model.

Understanding Feature Scope

• Sharepoint 2010 Can be scoped to Farm, Web Application, Site Collection, and Web Site level.
• Feature Scope id defined by Scope attribute in feature.xml
• Sample Feature will look like this

<Feature Id=”F62C96CF-79FD-44be-8882-E9BFBD199184″

Title=”Feature Title”

Description=”Feature Description”

Version=”1.0.0.0″

Scope=”Site”

Hidden=”false”>

</Feature>

Web Site scoped Feature (Scope=”Web”)

• Web Site Scoped feature can be activated at individual Web site level.
• List Instances, Event Receivers, Custom Actions etc are the custom elements for Website scope features.
• It can be activated by STSADM command like ” stsadm “o installfeature “name FeatureFolderName “url http://sharepointserver/site/subsite
• Alternatively open site features page by site actions -> site settings -> modify all site settings ->site features and click activate.

Site Collection scoped Feature (Scope=”Site”)

• Site Collection Scoped feature can be activated at the site collection level.
• It can contains item that can apply to Site Collection as a whole like content types that are shared across the site collection, as well as items that can be activated per site for e.g. List Instances, Event Receivers, Custom Actions etc
• It can be activated by STSADM command like ” stsadm “o installfeature “name FeatureFolderName “url http://sharepointserver/site/sitecollectionname
• Alternatively open site features page by site actions -> site settings -> modify all site settings ->site features and click activate.

Web Application scoped Feature (Scope=”WebApplication”)

• Web Application Scoped feature can be activated at the Web application level.
• It can contains item like administrative web application links, delegate control registrations, document forms registration etc.
• It can be activated by STSADM command like ” stsadm “o installfeature “name FeatureFolderName “url http://sharepointserver
• Alternatively open Manage Web Application Features from Central Administrator Central Administrator -> Application Management -> Manage Application Features and click activate.

Farm scoped Feature (Scope=”Farm”)

• Farm Scoped feature can be activated at the Farm level.
• It can contain number of element like application logic etc which can be applicable anywhere within deployment. It contacts links to /_layouts pages and files, /_admin pages etc.
• It can be activated by STSADM command like ” stsadm “o installfeature “name FeatureFolderName
• Alternatively open Manage Farm Features from Central Administrator Central Administrator -> Operations -> Manage Application Features and click activate.
• Farm scope feature will be activated automatically once it is installed on server.

References

http://msdn.microsoft.com/en-us/library/ms460318.aspx

http://www.etechplanet.com/blog/understanding-scope-of-sharepoint-features-(wss-30moss-2007).aspx

The post Understanding Features and Feature Scope in SharePoint 2010 appeared first on Pritam's Blog.

Exceeding any of Supported limits may cause Performance Issue in SharePoint 2010.

• Maximum size of Document in SharePoint 2010 is 2GB
• Default Threshold of Document Size in SharePoint 2010 is 50MB
• 250000 maximum recommended number of site collections per Web application is supported in SharePoint 2010
• 300 Content Databases Per Web Application are supported
• Maximum 5 Zones per Web Application. (Default, Intranet, Internet, Extranet, and Custom. Zones limit defined for farm is hard-coded.
• Managed paths are cached on the Web server, and CPU resources are used to process incoming requests against the managed path list. Maximum 20 number of Managed Path per Web Application supported.
• Maximum 300 MB Solution Cache Size per Web Application. The solution cache allows the InfoPath Forms service to hold solutions in cache in order to speed up retrieval of the solutions.

References:

http://technet.microsoft.com/en-us/library/cc262787.aspx

The post Web Application Limits and Boundaries in SharePoint 2010 appeared first on Pritam's Blog.

• AJAX is Asynchronous JavaScript And XML.
• The XmlHttpRequest is an actual object which works behind the scene.
• Ajax implementation uses JavaScript functions to call methods from a webservice, webpage request in response to get response.
• Response data is parsed using DOM.
• Asynchronous data retrieval using XmlHttpRequest

Advantages of AJAX

• Reduce the traffic travels between the client and the server.
• Response time is faster so increases performance and speed.
• You can use JSON (JavaScript Object Notation) which is alternative to XML. JSON is key value pair and works like an array.
• You can use Firefox browser with an add-on called as Firebug to debug all Ajax calls.
• Ready Open source JavaScript libraries available for use – JQuery, Prototype, Scriptaculous, etc..
• AJAX communicates over HTTP Protocol.

Disadvantages of AJAX

• It can increase design and development time
• More complex than building classic web application
• Security is less in AJAX application as all files are downloaded at client side.
• Search Engine like Google cannot index AJAX pages.
• JavaScript disabled browsers cannot use the application.
• Due to security constraints, you can only use it to access information from the host that served the initial page. If you need to display information from another server, it is not possible within the AJAX.

The post What is AJAX appeared first on Pritam's Blog.

Garbage Collector provide automatic Memory Management in .NET. It is Component of .net CLR (Common Language Runtime). Follow are the advantages of Garbage Collection –

• It allocates memory objects on heap efficiently.
• Develop application without worrying about releasing of memory.
• Reclaims object that are no longer in use, clear their memory and keep it available for future memory allocations.
• Memory Safe as cannot direct access memory of other objects.

Fundamentals of Memory –

• Each process has its own, separate virtual address space; on 32-bit computers each process has a 2-GB user-mode virtual address space.
• Garbage collector is responsible for Allocation and frees virtual memory on Managed Heap.
• Virtual memory can be in three state – FREE , RESERVED, COMMITTED
• We can run out of memory if run out of virtual address space to reserve or physical space to commit.

When Garbage Collection runs-

• System has low physical memory
• The memory that is used by allocated objects on the managed heap surpasses an acceptable threshold. This means that a threshold of acceptable memory usage has been exceeded on the managed heap. This threshold is continuously adjusted as the process runs.
• The GC.Collect method is called. In almost all cases, you do not have to call this method, because the garbage collector runs continuously. This method is primarily used for unique situations and testing.

What is Managed Heap?

• Garbage Collector allocates segment of memory for objects which is called Managed Heap.
• Each managed process has managed heap.
• Win32 VirtualAlloc and VirtualFree functions called by garbage collector to reserve or release segment of memory.
• After triggering Garbage Collector, it reclaims the memory occupied by dead objects and compact live objects so they live together. This process will make heap smaller.
• Heap can be considered as : Large Object Heap and Small Object Heap
• Objects with size 85000 bytes and larger will go on Large Object Heap.

Generations

• Heap is organized into generations which can easily handle long live objects and short lived objects.
• There are three generations – Generation 0 , Generation 1, Generation 2
• Generation 0 – This is youngest generation for newly created objects. Garbage collector reclaims memory from this Generation most frequently. For e.g. Temporary variables, new objects
• Generation 1 – Short lived objects are resides in this generation. As soon as Garbage collector starts reclaiming memory, objects from Generation 0 will move to Generation 1 if they are still in use.
• Generation 2 – Long lived objects are resides in this generation. For e.g. Static variables.

You can find detailed article on – http://msdn.microsoft.com/en-us/library/ee787088.aspx

The post Garbage Collection in .NET appeared first on Pritam's Blog.

• SOAP is an XML-based messaging framework specifically designed for exchanging formatted data across the Internet, for example using request and reply messages or sending entire documents.
• completely neutral with respect to operating system, programming language, or distributed computing platform
• A better way was needed to describe the messages and how they are exchanged. The Web Services Description Language (WSDL) is a particular form of an XML Schema, developed by Microsoft and IBM for the purpose of defining the XML message, operation, and protocol mapping of a web service accessed using SOAP or other XML protocol.
• The WSDL syntax allows both the messages and the operations on the messages to be defined abstractly, so they can be mapped to multiple physical implementations.
• WSDL creates web service definitions by mapping a group of endpoints into a logical sequence of operations on XML messages. The same XML message can be mapped to multiple operations (or services) and bound to one or more communications protocols (using “ports”).
• The Universal Description, Discovery, and Integration (UDDI) framework defines a data model (in XML) and SOAP APIs for registration and searches on business information, including the web services a business exposes to the Internet.
• UDDI is an independent consortium of vendors, founded by Microsoft, IBM, and Ariba, for the purpose of developing an Internet standard for web service description registration and discovery.
• The information in UDDI is categorized according to industry type and geographical location, allowing UDDI consumers to search through lists of potentially matching businesses to find the specific one they want to contact.
• When you create a Web reference, Visual Studio creates an XML Web service proxy class automatically and adds it to your project. This proxy class exposes the methods of the XML Web service and handles the marshalling of appropriate arguments back and forth between the XML Web service and your application. Visual Studio uses the Web Services Description Language (WSDL) to create the proxy.

The post Web Service in ASP.Net (SOAP) appeared first on Pritam's Blog.