Posts

Showing posts from January, 2014

Server Object Model in SharePoint 2013

Image
What is Object Model ? An object model is group of objects related to each other using Has-a Relationship. Let us See the below figure. You will get Clear idea on SharePoint Farm . Open visual studio 2012-->File-->New-->Select Console Application Template(Select Visual C# on Left Side)-->give Proper Name Click on Ok. Go to Build-->Configuration Manager-->select X64 at Activation Solution platform. One more Important Point Here You want to add reference--> Microsoft.sharePoint.dll Get All Web Applications in a Farm: Add Name Spaces: Using MicroSoft.SharePoint; Using MicroSoft.SharePoint.Administration SPFarm farm = SPFarm.Local;             foreach (SPService service in farm.Services)             {                 if (service is SPWebService)  ...

Create a New WebApplication Using PowerShell

Image
Open SharePoint Management Shell Or Windows Power-Shell In this article I am going to Explain on Windows Power-Shell Open Windows Power-Shell, Add Snapin U just type this Cmdlet Add-PSSnapin "Microsoft.SharePoint.PowrShell". New We are going to Create New Web application: New-WebApplcation -ApplicationPool SharePoint-80 -Name sp2013-80 -ApplicationPoolAccount SPDOMSERVER\Administrator -Port 80 If you do not include the port number, a random port number will be assigned. The first web application created will use port 80.   New Web Application is Created but it is a classic Mode . Every One  rise the question how to change the classic to claims base authentication. Then Simply, ClickHere

How to convert Web application from Classic Mode authentication to Claims based Authentication

Image
Follow PowerShell commands to convert the web application from Classic Mode Authentication to Claims based Authentication: Go to CA-->Application Management-->Click on Manage Web Applications--> Click On your Classic based Authentication Web Application and you will find Authentication Providers on ribbon Interface, U will find the following Figure.    It is a windows or classic base authentication. Go to windows PowerShell, Type following CmdLets $App=Get-SPWebApplication "http://sp2013/" $App.UseClaimsAuthentication ="True" $App.Update() Or u Will find the Below Figure After that, Go to Central administration  Check It is a Claims Based Authentication or not I think it is clear to any one..thanks for visiting my blog .....

Different between Restrict Delete and Cascade Delete in List

Image
    Restrict Delete: It Means that users cannot delete the data in Batch list if the data is referenced. They can only delete the data in the parent list only if the referenced data in the child list is completely deleted. So, if we want to delete an item in Batch we have to delete the Product list data that is using ‘Batch′. SharePoint will give the following error if we try to delete until all references are deleted. Cascade delete:  It means that users can delete the data in Batch list though the data is referenced. But, once we delete the item in the Batch list all the items that referred in the Product list will also be deleted. While deleting it will give popup message which list is referencing its data and that data will also be deleted as in the following image  
Image
Error while Installing SQL Server 2012 with NetFx3 Okay… I am installing SQL Server 2012 on a Windows Server 2012 box, there shouldn’t be any problems.  Everything is proceeding normally until I get this message: Error while enabling Windows feature : NetFx3, Error Code : –2146498298 , Please try enabling Windows Feature : NetFx3 from Windows management tools and then run setup again. No problem… I know how to install Windows Features; I start the Add roles and Features Wizard and go looking for NetFx3… it’s not there. Problem. It turns out that Windows Server 2012 does not include NetFx3 when it is installing.  It doesn’t mean that it is gone, but it does have to be installed separately.  Here’s what you do: 1) Insert your Windows Server 2012 media.  As I was installing SQL Server in a Hyper-V VM I ejected the SQL media and attached my Windows Server 2012 ISO.  I t...