Q. What is SharePoint 2010?

Def : SharePoint 2010 is the business collaboration platform for the Enterprise & the Web that enables you to connect & empower people through an integrated set of rich features. Whether deployed on-premises or as hosted services, SharePoint 2010 helps you cut costs with a unified infrastructure while allowing you to rapidly respond to your business needs.

Q. What Has Changed with 12 hive in SharePoint? Ans. Three New Folders have been added in 12 hive structure. UserCode files used to support sandboxed solutions . WebClients used for the client Object Model. WebServices .svc files . See SharePoint 2010 Object Model

Q. How would you re-deploy the old custom solutions in SharePoint 2010.What Changes are needed to the old Solution files. Ans. SharePoint 2010 object model contains many changes and enhancements, but our custom code will still compile and, will run as expected. You should however, rewrite and recompile any code that refers to files and resources in "12 hive". For Details See : See SharePoint 2010 Object Model - Backward Compatibility

Q. Whats New with SharePoint WebParts? A developer can create two types of webparts using Visual Studio 2010. 1. Visual Webparts - Allows you to Drag and Drop the controls from the Toolbox to WebPart Design surface. You can of course write your custom code in the code file. You can also package and deploy your webparts directly to Sharepoint from VS by pressing Clt+F5. Visual studio 2010 also provides you with three different views for developing webparts. The views are split view, design view and Source view(as we have in designer 2007). Note : The Visual Webpart project Item basically loads a User Control as a WebPart.

2. ASP.Net WebParts - Where a developer can build up User Interface and logic in a class file. You do not have designer for drag and drop of controls. This webpart inherits from standard ASP.Net webpart. For Deployment we can again use ctrl+f5 to deploy this webpart.

Q. What are the Visual Studio 2010 Tools for SharePoint. Ans. Visual Studio 2010 includes SharePoint-specific project types and project item types, and includes powerful packaging, deployment, and debugging features that help increase your efficiency as a SharePoint 2010 developer. Some of the Templates avaiable are : 1.Visual Web Part project template. 2. List defination template. 3. Content Type template. 4. Empty Project template. 5. Event Receiver template. 6. some workflow template. 7. the Site Definition template and many more....

Q. What are SharePoint Sandboxed soultions ? Ans. SharePoint 2010 provides a new sandboxed environment that enables you to run user solutions without affecting the rest of the SharePoint farm. This environment means that users can upload their own custom solutions without requiring intervention from administrators, and without putting the rest of the farm at risk. This means that the existing sites\pages or components will not be effected by the newly added soultion. Users can deploy the below four things as sandboxed soultions : 1. WebParts. 2. Event Receivers. 3. List Definations. 4. Workflows.

Q. What are Requirenments for SharePoint 2010.

Ans. SharePoint Server 2010 will support only 64 - bit. It will require 64 bit Windows Server 2008 or 64 bit Windows Server 2008 R2. In addition to this, it will require 64 bit version of SQL Server 2008 or 64-bit version of SQL Server 2005.

Q. What is LINQ. How is it used in Sharepoint ? Ans. LINQ is a feature of the programming languages C# 3.0 and Visual Basic .NET. LINQ allows you to query in an object-oriented way, supports compile-time check, gives you intellisense support in Visual Studio and defines a unified, SQL like syntax to query any data source. But unlike other languages and query syntaxes which vary from one type of data source to another, LINQ can be used to query, in principle, any data source whatsoever. Hence, developers may find that it is the only query syntax that they ever need to know. It is commonly used to query objects collections, XML and SQL server data sources. LINQ to SharePoint is officially being supported with the 2010 release.It works similar to LINQ to SQL or LINQ to Entity. The LINQ to SharePoint Provider is defined in the Microsoft.SharePoint.Linq namespace. It translates LINQ queries into Collaborative Application Markup Language (CAML) queries.The gateway class for the LINQ to SharePoint provider is Microsoft.SharePoint.Linq.DataContext which represents the data of a SharePoint Foundation Web site. The following is an example of the use of LINQ to query SharePoint Foundation: // Get DataContext from page context DataContext data = new DataContext(SPContext.GetContext(this.Context).Web.Url); // Get the SharePoint list EntityList Customers = data.GetList("Customers"); // Query for customers from London var londonCustomers = from customer in Customers where customer.City == "London" select customer; foreach (var londonCust in londonCustomers) { Console.Writeline("id = {0}, City = {1}", londonCust.CustomerId,

londonCust.City); } LINQ, However is an extra layer to the actual CAML query.

Q. What Changes are made in SharePoint 2010 to enforce Referential Integrity? Ans. In SharePoint 2010, Referential Integrity is enforced using two options, available with Look-up columns. While creating a Look-up column, you can either choose a) Restrict Delete or b) Cascade Delete to define a relationship between the Look-up list and the list containing the look-up Column. Read Details at SharePoint 2010 Referential integrity - Using LookUp Column

Q. Whats Ribbon in SharePoint 2010? Ans. See the Post Ribbon in SharePoint 2010

Q . Whats New in SPALerts ? Ans. In SharePoint 2007, alerts were send only through e-mails, but in SP2010 users can also send an alert to mobile devices as SMS Message. A New property DeliveryChannels is introduced to indicate, whether the alert is delivered as E-mail or as an SMS Message.

Q. What Has Changed with SSP in SharePoint 2010. Ans. In SharePoint 2010 Shared Service Providers (SSP's) are replaced by Service Applications. Services are no longer combined into a SSP. They are running independent as a service application. The service application architecture is now also built into Microsoft SharePoint Foundation 2010, in contrast to the Shared Services Provider (SSP) architecture that was only part of Office SharePoint Server 2007.

A key benefit here is that all services are installed by default and there is no SSP setup.