Explore topic-wise InterviewSolutions in .

SuiteLinksDelegate Delegate CONTROL is responsible for displaying Links “NewsFeed, SkyDrive and Sites” in top right of the NEW SharePoint 2013 SITE (in the blue bar). These Links can be REPLACED by Overriding SuiteLinksDelegate Delegate Control using a Custom Control Created using Visual Studio

SuiteLinksDelegate Delegate Control is responsible for displaying Links “NewsFeed, SkyDrive and Sites” in top right of the new SharePoint 2013 site (in the blue bar). These Links can be replaced by Overriding SuiteLinksDelegate Delegate Control using a Custom Control Created using Visual Studio

SuiteBarBrandingDelegate DELEGATE Control is responsible for displaying ‘SharePoint’ or ‘Office 365′ text on TOP LEFT of the new SharePoint 2013 site (in the blue bar). This text can only be replaced by OVERRIDING SuiteBarBrandingDelegate Delegate Control with a custom Custom Control Created using VISUAL Studio.

SuiteBarBrandingDelegate Delegate Control is responsible for displaying ‘SharePoint’ or ‘Office 365′ text on top left of the new SharePoint 2013 site (in the blue bar). This text can only be replaced by Overriding SuiteBarBrandingDelegate Delegate Control with a custom Custom Control Created using Visual Studio.

Yes.You Can de-activiate Follow & SOCIAL by disabling following Content feature and site Feeds feature on the Team site(in the WRITTEN Order).By DEFAULT, the Site feed feature on a team site is enabled.

Yes.You Can de-activiate Follow & Social by disabling following Content feature and site Feeds feature on the Team site(in the written Order).By default, the Site feed feature on a team site is enabled.

1. Backup and Restore SharePoint 2010 Content database in your SharePoint 2013 farm.
2. Run Test-SPContentDatabase cmdlet to identify missing Components along with potential ERRORS and related warnings. CHECK the upgrade log and DEPLOY any missing components and re-run the cmdlet to verify.
3. Attach the Content database to the DESIRED web application using Mount-SPContentDatabase cmdlet.
4. After successfully mounting the content database to web application, the site should be accessible in 14 mode.
5. Next, to Upgrade the site to 15 Hive, Navigate to SiteUpgrade.aspx page in Site Setting of your site collection.
6. Click on “Upgrade the Site Collection” BUTTON.
7. During the upgrade The SiteUpgrade.aspx page shows the progress and provides a link to an upgrade log for troubleshooting purposes.
8. Site Collection Should now be accessible in 15 mode.

As per MSDN, Microsoft is not CREATING any NEW Versions of these Templates.The old SITES based on these templates Can be UPGRADED only if the Templates are Installed successfully in SharePoint 2013.You can try installing wsp of Fab 40 with CompatabilityLevel as 15 and upgrade the existing site collections.

As per MSDN, Microsoft is not Creating any New Versions of these Templates.The old Sites based on these templates Can be upgraded only if the Templates are Installed successfully in SharePoint 2013.You can try installing wsp of Fab 40 with CompatabilityLevel as 15 and upgrade the existing site collections.

MASTER Pages and Css has Changed a lot in SHAREPOINT 2013.You can deploy a master page in Master page GALLERY but the STYLES from old core.css NEEDS to be updated.

Master Pages and Css has Changed a lot in SharePoint 2013.You can deploy a master page in Master page gallery but the styles from old core.css needs to be updated.

In SharePoint 2013 with the new COMPATIBILITY Level PARAMETER of Install-SPSolution cmdlet you can now DEPLOY your wsp Solutions to 14 hive, 15 hive or both.

In SharePoint 2013 with the new compatibility Level parameter of Install-SPSolution cmdlet you can now Deploy your wsp Solutions to 14 hive, 15 hive or both.

If the solution was Created in Visual STUDIO 2010, you would add SharePointVersion=”15.0″ attribute in Solution’s manifest.xml file to force it to deploy in 15 Hive instead of 14 Hive.If the Solution however is Created in Visual Studio 2012, you don’t need to do anything, it GETS DEPLOYED to 15 Hive by DEFAULT.

If the solution was Created in Visual Studio 2010, you would add SharePointVersion=”15.0″ attribute in Solution’s manifest.xml file to force it to deploy in 15 Hive instead of 14 Hive.If the Solution however is Created in Visual Studio 2012, you don’t need to do anything, it gets deployed to 15 Hive by default.

The CODE for an APP runs in DIFFERENT places, depending on where your app is hosted.They never RUN in the context of SharePoint SERVER, but they will run in the context of the browser or in the context of the hosted platform.You Can Develop three kind of Apps –SharePoint-hosted apps Provider-hosted and autohosted apps.In the cloudApps that have a mix of Components in SharePoint and in the cloud

The Code for an app runs in different places, depending on where your app is hosted.They never run in the context of SharePoint Server, but they will run in the context of the browser or in the context of the hosted platform.You Can Develop three kind of Apps –SharePoint-hosted apps Provider-hosted and autohosted apps.In the cloudApps that have a mix of Components in SharePoint and in the cloud

SHAREPOINT 2013 Introduces a Cloud APP MODEL that enables you to Create apps.Apps for SharePoint are self-contained pieces of functionality that extend the capabilities of a SharePoint website. An app may include SharePoint components such as lists, workflows, and site PAGES, but it can also surface a remote web application and remote data in SharePoint.To see how its different from Farm SOLUTION

SharePoint 2013 Introduces a Cloud App Model that enables you to Create apps.Apps for SharePoint are self-contained pieces of functionality that extend the capabilities of a SharePoint website. An app may include SharePoint components such as lists, workflows, and site pages, but it can also surface a remote web application and remote data in SharePoint.To see how its different from Farm solution

Apart from the new App Model for Creating Custom Components, Microsoft has added a few new Namespaces to work with newly added – Social,Event Receivers,Delegate Controls,CALLOUT Popups and other Custom Components in SharePoint 2013.In addition to these CLASSES a few new templates in VISUAL STUDIO 2012 has ALSO been added to Create better solutions.

Apart from the new App Model for Creating Custom Components, Microsoft has added a few new Namespaces to work with newly added – Social,Event Receivers,Delegate Controls,Callout Popups and other Custom Components in SharePoint 2013.In addition to these classes a few new templates in Visual Studio 2012 has also been added to Create better solutions.

In SHAREPOINT 2013 Microsoft has Introduced new Social Capabilities to LET users COLLABORATE Socially in the Company.My Sites have been enhanced Incredibly to INTEGRATE these Social features.Some of the new Features added are Community Sites,Microblogging,NewsfeedSite feed,Follow people and Follow Sites.

In SharePoint 2013 Microsoft has Introduced new Social Capabilities to let users Collaborate Socially in the Company.My Sites have been enhanced Incredibly to Integrate these Social features.Some of the new Features added are Community Sites,Microblogging,NewsfeedSite feed,Follow people and Follow Sites.

Cross-Site Publishing is a new Feature in SharePoint Server 2013 that enables you to REUSE CONTENT across site COLLECTIONS,WEB applications, and farms.You can use cross-site publishing to CREATE branded Internet, intranet and extranet publishing sites.

Cross-Site Publishing is a new Feature in SharePoint Server 2013 that enables you to reuse content across site collections,web applications, and farms.You can use cross-site publishing to Create branded Internet, intranet and extranet publishing sites.

A new Column type RELATED ITEMS has been Introduced in SharePoint 2013 where you can ADD reference to another Item or a document from any ListLibrary as a related ENTITY to ONE of the Item using Related Items column.

A new Column type related Items has been Introduced in SharePoint 2013 where you can add reference to another Item or a document from any ListLibrary as a related entity to one of the Item using Related Items column.

SharePoint 2013 was added with the new Out-of-Box Support for IFrames.Admins can now embed dynamic content from other sites, such youtube videos or maps to any SharePoint site by USING IFrames. Admins would need to add the Domain for the external site in TML FIELD Security first.

SharePoint 2013 was added with the new Out-of-Box Support for IFrames.Admins can now embed dynamic content from other sites, such youtube videos or maps to any SharePoint site by using IFrames. Admins would need to add the Domain for the external site in TML Field Security first.

Image renditions ENABLE you to RENDER a single image in multiple ways. An image can be displayed in various SIZES or with different CROPPING.

Image renditions enable you to render a single image in multiple ways. An image can be displayed in various sizes or with different cropping.

SharePoint 2013 supports two Video players – HTML 5 player and a Silverlight player.SharePoint CHOOSES the player AUTOMATICALLY, depending on the video format that it ENCOUNTERS in the video set (the COLLECTION of files that are RELATED to the video). If the format can be played on the HTML 5 player, the SharePoint uses the Silverlight player.

SharePoint 2013 supports two Video players – HTML 5 player and a Silverlight player.SharePoint chooses the player automatically, depending on the video format that it encounters in the video set (the collection of files that are related to the video). If the format can be played on the HTML 5 player, the SharePoint uses the Silverlight player.

Video Content type added to SharePoint 2013 is a very useful addition for Content Authors.The Improved Assets Library provides support for Video Content Types and provides various Out-of-Box views LIKE ?thumbnails?and Out-of-Box pages like ?IDEO PAGE?to View Videos in a very Interactive way.

Videos in SharePoint 2013 are ORGANIZED in a manner similar to “document sets”. SharePoint Creates a stub (think of it as a folder) to hold a video and all the related contents, such as user-defined properties, thumbnails, video renditions, and other documents related to the video. You can use the Video Content Type in Asserts Library properties.

Video Content type added to SharePoint 2013 is a very useful addition for Content Authors.The Improved Assets Library provides support for Video Content Types and provides various Out-of-Box views like ?thumbnails?and Out-of-Box pages like ?ideo Page?to View Videos in a very Interactive way.

Videos in SharePoint 2013 are Organized in a manner similar to “document sets”. SharePoint Creates a stub (think of it as a folder) to hold a video and all the related contents, such as user-defined properties, thumbnails, video renditions, and other documents related to the video. You can use the Video Content Type in Asserts Library properties.

In SharePoint 2013 MICROSOFT has INTRODUCED a new SET of content types called digital Asset Content Types?for better USE of AUDIO, Video and Images as Web Content.These content types can be added to any library and can be used as a one of the items files.

In SharePoint 2013 Microsoft has introduced a new set of content types called digital Asset Content Types?for better use of Audio, Video and Images as Web Content.These content types can be added to any library and can be used as a one of the items files.

SharePoint 2013 provides a support to get ?mbed INFORMATION?for documents and other DIGITAL Content types such as Videos,AUDIOS etc. to be added on any SharePoint Page or in a Microblogging feed.

SharePoint 2013 provides a support to get ?mbed Information?for documents and other digital Content types such as Videos,Audios etc. to be added on any SharePoint Page or in a Microblogging feed.

SHAREPOINT 2013 now offers Out-of-box PDF Support and what that REALLY means is that PDF icon is now natively supported and PDF when opened in SharePoint 2013 will TRY to open in the Adobe Reader and prompt USER to either checkout & open or open the FILE in PDF directly.

SharePoint 2013 now offers Out-of-box PDF Support and what that really means is that PDF icon is now natively supported and PDF when opened in SharePoint 2013 will try to open in the Adobe Reader and prompt user to either checkout & open or open the file in PDF directly.

For End users and CONTRIBUTORS, some very Interactive features such as Drag and Drop of documents,Convert to PDF(Print to pdf),QUICK edit (datasheet VIEW),Document Library SEARCH(Find a File),Get Embed code for documents and Out of BOX PDF Support etc. has been added in Web Content Management.

For End users and Contributors, some very Interactive features such as Drag and Drop of documents,Convert to PDF(Print to pdf),Quick edit (datasheet view),Document Library Search(Find a File),Get Embed code for documents and Out of box PDF Support etc. has been added in Web Content Management.

The Distributed Cache service provides caching features in SharePoint Server 2013. The microblog features and FEEDS rely on the Distributed Cache to store data for very fast retrieval ACROSS all entities. The Distributed Cache service is BUILT on Windows Server AppFabric, which implements the AppFabric Caching service. Windows Server AppFabric INSTALLS with the prerequisites for SharePoint Server 2013.

The Distributed Cache service provides caching features in SharePoint Server 2013. The microblog features and feeds rely on the Distributed Cache to store data for very fast retrieval across all entities. The Distributed Cache service is built on Windows Server AppFabric, which implements the AppFabric Caching service. Windows Server AppFabric installs with the prerequisites for SharePoint Server 2013.

In SharePoint 2013 with the new Compatibility Level parameter of INSTALL -SPSolution cmdlet you can now DEPLOY your .wsp or SOLUTION to EITHER 14 hive or 15 hive or both.

In SharePoint 2013 with the new Compatibility Level parameter of Install -SPSolution cmdlet you can now deploy your .wsp or Solution to either 14 hive or 15 hive or both.

Device CHANNEL Panel is a new CONTROL that you can INCLUDE in a PAGE layout to control what content is rendered in which channel. The Device Channel Panel is a container that is MAPPED to one or more channels.

Device Channel Panel is a new control that you can include in a page layout to control what content is rendered in which channel. The Device Channel Panel is a container that is mapped to one or more channels.

With DEVICE channels in SharePoint 2013, you can render a single publishing site in multiple ways by USING different designs that target different devices for example mobile devices etc.These device channels can each be given a different master page and CSS file to GIVE users a more OPTIMAL viewing experience.

With device channels in SharePoint 2013, you can render a single publishing site in multiple ways by using different designs that target different devices for example mobile devices etc.These device channels can each be given a different master page and CSS file to give users a more optimal viewing experience.

The Analytics Processing Component runs TWO main types of analyses: Search analytics and Usage analytics. Search analytics ANALYZES content in the search index, and usage analytics analyzes the user ACTIONS.

The Analytics Processing Component runs two main types of analyses: Search analytics and Usage analytics. Search analytics analyzes content in the search index, and usage analytics analyzes the user actions.

The Analytics Processing Component in SharePoint Server 2013 analyzes both the Content and the way USERS INTERACT with it.The RESULTS from the ANALYSIS are added to the items in the search index to be used by Search Webparts,RECOMMENDATION Reports,Most Popular Items reports and other WebParts.

The Analytics Processing Component in SharePoint Server 2013 analyzes both the Content and the way users interact with it.The results from the analysis are added to the items in the search index to be used by Search Webparts,Recommendation Reports,Most Popular Items reports and other WebParts.

Every Document in SharePoint 2013 is now stored as multiple threaded BLOBS in the new Streams data table. WHENEVER a new VERSION of a document is created, a new Record is written in this data table that CONTAINS only the thread BLOBS of the original document that corresponds to the Change, merged with the new Changes.

In other words a new Blob with Changes is added as a new row in the table. Each BLOB that gets added Contains a numerical Id that represents the source BLOB.

At the end it is the job of BLOB Index to keep the track of Blobs and to create a full file with the Combination of entries that point to the unchanged shreds of the previous version(s) and the entries that point to the newly added Changed shreds.

Every Document in SharePoint 2013 is now stored as multiple threaded BLOBS in the new Streams data table. Whenever a new Version of a document is created, a new Record is written in this data table that contains only the thread BLOBS of the original document that corresponds to the Change, merged with the new Changes.

In other words a new Blob with Changes is added as a new row in the table. Each BLOB that gets added Contains a numerical Id that represents the source BLOB.

At the end it is the job of BLOB Index to keep the track of Blobs and to create a full file with the Combination of entries that point to the unchanged shreds of the previous version(s) and the entries that point to the newly added Changed shreds.

Minimal Download Strategy in SHAREPOINT 2013 improves rendering performance when browsing content where large parts of the page do not CHANGE providing a more fluid navigation experience. For example when NAVIGATING between a site? home page and Shared Documents page only the Content that has changed between the source and destination page (controls and placeholders in the content area) are downloaded and URL subsequently updated where the chrome is persisted.

Minimal Download Strategy in SharePoint 2013 improves rendering performance when browsing content where large parts of the page do not change providing a more fluid navigation experience. For example when navigating between a site? home page and Shared Documents page only the Content that has changed between the source and destination page (controls and placeholders in the content area) are downloaded and Url subsequently updated where the chrome is persisted.

SHAREPOINT 2013 Introduces Minimal DOWNLOAD Strategy and Distributed Cache Service to IMPROVE Page Load; and Shredded Storage to Improve Storage required for SAVING files.

SharePoint 2013 Introduces Minimal Download Strategy and Distributed Cache Service to Improve Page Load; and Shredded Storage to Improve Storage required for saving files.

With SharePoint 2013 Microsoft has Introduced User LICENSE Enforcement Capabilities – that means different licenses can be assigned to different USERS based on Active Directory security groups that are added in.

A group of ADMINS for example WOULD need features that are offered by Enterprise license but a group end users on the other hand can work with Standard license and would not need to PAY more.

By default the User License Enforcement is disabled and must first be enabled to begin assigning, using, and implementing user licensing capabilities.

With SharePoint 2013 Microsoft has Introduced User License Enforcement Capabilities – that means different licenses can be assigned to different users based on Active Directory security groups that are added in.

A group of admins for example would need features that are offered by Enterprise license but a group end users on the other hand can work with Standard license and would not need to pay more.

By default the User License Enforcement is disabled and must first be enabled to begin assigning, using, and implementing user licensing capabilities.

Microsoft has added some Incredible features to SHAREPOINT 2013 that can be of huge benefit to all the Companies that USE SharePoint on a large scale. Most of the new Features are INTRODUCED for Improving SharePoint Performance (for both Browser and SQL) and to enhance the famous WEB Content Management Capabilities.There is an Improvement for all – end users, developers and IT ADMINISTRATORS.

Microsoft has added some Incredible features to SharePoint 2013 that can be of huge benefit to all the Companies that use SharePoint on a large scale. Most of the new Features are Introduced for Improving SharePoint Performance (for both Browser and SQL) and to enhance the famous Web Content Management Capabilities.There is an Improvement for all – end users, developers and IT administrators.

SHAREPOINT 2013 Introduces a new “Getting STARTED” WebPart that has “Tiles” to PROVIDE an easy access to some of the MAIN links in the Site like – adding listslibraries,Creating masterpage etc.To Programmatically Create this new WebPart a new abstract base class TilesViewWebPart has been added in SharePoint API.You have to Create a Custom Webpart and Inherit from TilesViewWebpart and OVERRIDE GetTiles() to Create Custom tiles.

SharePoint 2013 Introduces a new “Getting Started” WebPart that has “Tiles” to provide an easy access to some of the main links in the Site like – adding listslibraries,Creating masterpage etc.To Programmatically Create this new WebPart a new abstract base class TilesViewWebPart has been added in SharePoint API.You have to Create a Custom Webpart and Inherit from TilesViewWebpart and Override GetTiles() to Create Custom tiles.

A new Visual WEBPART Template has been added to Visual Studio 2012 for Creating Visual Webparts for SharePoint 2013. In this new Template both the User Control and WebPart Classes are MERGED to Create ONE template unlike SharePoint 2010 where you had a SEPARATE ascx and webpart file.Also, now you can Create both Sandbox and Farm solutions using Visual WebPart Template.

A new Visual WebPart Template has been added to Visual Studio 2012 for Creating Visual Webparts for SharePoint 2013. In this new Template both the User Control and WebPart Classes are merged to Create one template unlike SharePoint 2010 where you had a separate ascx and webpart file.Also, now you can Create both Sandbox and Farm solutions using Visual WebPart Template.

SANDBOX SOLUTIONS are UPGRADED with the CONTENT DATABASES.

Sandbox Solutions are upgraded with the Content databases.

You can no longer add partial trust SOLUTION Packages to the bin directory.Any files deployed to the bin directory must be full trust. Any deployment scripts needs to be updated to make SURE that they specify the correct trust level. After the release of .NET Framework 4.0, the GAC was split into two, one for each CLR.

c:windowsassembly is the location for .NET versions 1.0 through 3.5 and c:windowsmicrosoft.netassembly is location for all the dlls for project CREATED in .NET Framework 4.0.

You can no longer add partial trust Solution Packages to the bin directory.Any files deployed to the bin directory must be full trust. Any deployment scripts needs to be updated to make sure that they specify the correct trust level. After the release of .NET Framework 4.0, the GAC was split into two, one for each CLR.

c:windowsassembly is the location for .NET versions 1.0 through 3.5 and c:windowsmicrosoft.netassembly is location for all the dlls for project Created in .NET Framework 4.0.

YES. A CUSTOM Result TYPE and Display template WOULD be needed.

Yes. A Custom Result type and Display template would be needed.

Similar to DIALOG framework in SharePoint 2010, Microsoft has added a new Callout POPUP framework to Create HOVER Popups that you know as PREVIEW Windows as well. These NotificationTooltipHelp (whatever you call it..) Callout Popups can be fully Customized to ADD Custom Text & Actions for guiding End-users.For more details see The new Hover OverPreviewCallout Popups in SharePoint 2013

Similar to Dialog framework in SharePoint 2010, Microsoft has added a new Callout Popup framework to Create Hover Popups that you know as Preview Windows as well. These NotificationTooltipHelp (whatever you call it..) Callout Popups can be fully Customized to add Custom Text & Actions for guiding End-users.For more details see The new Hover OverPreviewCallout Popups in SharePoint 2013

No. DIALOG FRAMEWORK STILL EXISTS.

No. Dialog Framework still exists.

NEW “SPField.JSLink” property has been added to help specify any EXTERNAL JavaScript file Containing any Rendering logic for Out-of-Box or Custom FIELD type.With JSLink developers can now Control the Rendering (the presentation and validation) of any Field (Custom or Out-of-box) on List forms as well as in Views by simply ADDING a reference to an External or deployed JavaScript file.

New “SPField.JSLink” property has been added to help specify any external JavaScript file Containing any Rendering logic for Out-of-Box or Custom field type.With JSLink developers can now Control the Rendering (the presentation and validation) of any Field (Custom or Out-of-box) on List forms as well as in Views by simply adding a reference to an External or deployed JavaScript file.

Sandbox Solutions are depreciated in SharePoint 2013.You can STILL Create them and DEPLOY them but they are not SUPPORTED by Microsoft (not 100% sure about this THOUGH).

Sandbox Solutions are depreciated in SharePoint 2013.You can still Create them and deploy them but they are not supported by Microsoft (not 100% sure about this though).

YES. SHAREPOINT 2013 provides SUPPORT for both 14 Hive and 15 Hive. Solutions from SharePoint 2010 can be deployed in SharePoint 2013 EITHER in 14 Hive,15 Hive or both. This can be done using the new “CompatibilityLevel” parameter of Install-SPSolution CMDLET with which you can now Deploy your wsp Solutions to 14 hive, 15 hive or both.

Yes. SharePoint 2013 provides Support for both 14 Hive and 15 Hive. Solutions from SharePoint 2010 can be deployed in SharePoint 2013 either in 14 Hive,15 Hive or both. This can be done using the new “CompatibilityLevel” parameter of Install-SPSolution cmdlet with which you can now Deploy your wsp Solutions to 14 hive, 15 hive or both.

ExecuteQuery GIVES you the option to MINIMIZE the number of roundtrips to the server from your CLIENT code. All the components loaded into the clientcontext are executed in one go.

ExecuteQuery gives you the option to minimize the number of roundtrips to the server from your client code. All the components loaded into the clientcontext are executed in one go.

The ECMASCRIPT library is available in a number of JS files in the LAYOUTS folder. The main file among number of .js files is SP.js. When you include this file in the ASPX page using a ScriptLink control, all other required JS files are loaded AUTOMATICALLY.

By linking SP.js to your page, the SP namespace GETS registered. SP is the SharePoint namespace that contains all objects. For debugging purposes every js file also has a ‘debug’ equivalent in the same folder.

The ECMAScript library is available in a number of JS files in the LAYOUTS folder. The main file among number of .js files is SP.js. When you include this file in the ASPX page using a ScriptLink control, all other required JS files are loaded automatically.

By linking SP.js to your page, the SP namespace gets registered. SP is the SharePoint namespace that contains all objects. For debugging purposes every js file also has a ‘debug’ equivalent in the same folder.

Load METHOD populates the CLIENT object directly with what it gets data from the server i.e. a collection object LIKE ListItemCollection ETC. but LoadQuery returns the data as a completely new collection in IEnumerable format.

Other major difference is that the Collections that you load using the Load() method are eligible for GARBAGE collection only when the client context variable itself goes out of scope where as, in these collections go out of scope at the end of IEnumerable list

Load method populates the client object directly with what it gets data from the server i.e. a collection object like ListItemCollection etc. but LoadQuery returns the data as a completely new collection in IEnumerable format.

Other major difference is that the Collections that you load using the Load() method are eligible for garbage collection only when the client context variable itself goes out of scope where as, in these collections go out of scope at the end of IEnumerable list

Unlike CAML, with LINQ to SharePoint provider, you are working with strongly typed LIST item objects. For example, an item in the ANNOUNCEMENTS list is an object of type Announcement and an item on a Tasks list is an object of type Task. You can then enumerate the objects and get the PROPERTIES for your use. ALSO, you can use LINQ syntax and the LINQ keywords built into C# and VB for LINQ QUERIES.

Unlike CAML, with LINQ to SharePoint provider, you are working with strongly typed list item objects. For example, an item in the Announcements list is an object of type Announcement and an item on a Tasks list is an object of type Task. You can then enumerate the objects and get the properties for your use. Also, you can use LINQ syntax and the LINQ keywords built into C# and VB for LINQ queries.

The definitions for the out-of-the-box ribbon ELEMENTS are SPLIT across SEVERAL files in the SharePoint root, with TEMPLATE GLOBAL XML CMDUI.XML being the MAIN one.

The definitions for the out-of-the-box ribbon elements are split across several files in the SharePoint root, with TEMPLATE GLOBAL XML CMDUI.XML being the main one.

SharePoint site definitions are the core set of functionality from which SharePoint site are built from, building from the SiteTemplates directory in the SharePoint 12 hive.

Site definitions allow several sites to inherit from a core set of files on the file system, although appear to have unique pages, THEREBY increasing performance and ALLOWING changes that happen to a site propagate to all sites that inherit from a site DEFINITION.

Ghosted means that when SharePoint creates a new site it will reference the files in the related site definition upon site provisioning.

Unghosted means that the site has been edited with an external editor, and therefore the customizations are instead stored in the database, breaking the inheritance of those files from the file system.

SharePoint site definitions are the core set of functionality from which SharePoint site are built from, building from the SiteTemplates directory in the SharePoint 12 hive.

Site definitions allow several sites to inherit from a core set of files on the file system, although appear to have unique pages, thereby increasing performance and allowing changes that happen to a site propagate to all sites that inherit from a site definition.

Ghosted means that when SharePoint creates a new site it will reference the files in the related site definition upon site provisioning.

Unghosted means that the site has been edited with an external editor, and therefore the customizations are instead stored in the database, breaking the inheritance of those files from the file system.

This varies. GENERALLY, custom field controls inherit from the Microsoft.SharePoint.WebControls.BaseFieldControl namespace, but you can inherit from the DEFAULT field controls.

This varies. Generally, custom field controls inherit from the Microsoft.SharePoint.WebControls.BaseFieldControl namespace, but you can inherit from the default field controls.