Sharepoint - Asp.net - MVC - C# - Sql server - Jquery - Javascript

 On MSDN, the Join() operator mark as inefficient query and it will be possible only with LookUp fields. To avoid inefficient LINQ queries in SharePoint we can use LINQ to SharePoint provider and LINQ to Objects provider. The combination of these two providers can help us to deal with inefficient LINQ queries type. Prepare for Developing LINQ to SharePoint • SharePoint Lists - For this example I used two simple lists, joined with a regular CustomerID Text field Column. Customer List: Order List: To keep it simple, the columns in this example are all Single line of text fields • To use the LINQ to SharePoint Provider you need add this references Microsoft.SharePoint.Linq.dll and add the following using statement at the top of your class Microsoft.SharePoint.Linq using System.Linq; • To use LINQ to Objects add this reference System.Core.dll and add the following using statement at the top of your class using System.Linq; • To be able

Hi Friends, Please go through Following links for  ASP.Net MVC Interview Questions and answers. Its very usefull. Part 1 Part 2

This Article was founded at   Sharepoint 2013 In this article: Limits by hierarchy This section provides limits sorted by the logical hierarchy of a SharePoint Server 2013 farm. Web application limits The following table lists the recommended guidelines for web applications.   Limit Maximum value Limit type Notes Web application 20 per farm Supported We recommended limiting the number of web applications as much as possible. Create additional host named site collections where possible instead of adding web applications. Zone 5 per web application Boundary The number of zones defined for a farm is hard-coded to 5. Zones include Default, Intranet, Extranet, Internet, and custom. Managed path for host-named site collections 20 per farm Supported Managed paths for host-named site collections apply at the farm level. Each managed path that is created can be applied in any Web application. Mana