Working with Client Object Model in Microsoft Sharepoint

Microsoft SharePoint 2010 is the best-in-class platform for content management and collaboration. With Visual Studio, developers have an end-to-end business solutions development IDE. To leverage this powerful combination of tools it is necessary to understand the different building blocks of SharePoint.

In this article by Balaji Kithiganahalli, author of Microsoft SharePoint 2010 Development with Visual Studio 2010 Expert Cookbook, we will cover:

• Creating a list using a Client Object Model
• Handling exceptions
• Calling Object Model asynchronously

Microsoft LightSwitch: Querying and Filtering Data

The logic tier of LightSwitch basically starts with a data service that encapsulates all the access to the data source. This tier can host any number of data services exposed as endpoints at the service boundary. Each data service exposes a number of queryable entity sets with operations for querying entities and an operation for submitting changes; add, update, and delete. An entity set contains entities of the same entity type. All operations take place with entity sets whether they are intended for fetching or for making changes to them. If you think of an entity set as an analogue of SQL table you will not be wrong. Just like you take information out of the table, make changes to it and return it to the table, you do likewise with entity sets.

In this article by Jayaram Krishnaswamy, author of Microsoft Visual Studio LightSwitch Business Application Development, we will take a look at querying a single entity.

Digging into Windows Azure Diagnostics

A Windows Azure hosted service may comprise multiple instances of multiple roles. These instances all run in a remote Windows Azure data center—typically 24*7. The ability to monitor these instances non-intrusively is essential both in detecting failure and in capacity planning. This article by Neil Mackenzie, author of Microsoft Windows Azure Development Cookbook, shows how Windows Azure Diagnostics provides for the non-intrusive capture of diagnostic data and its subsequent persistence to the Windows Azure Storage Service. Windows Azure Diagnostics supports various standard sources, allowing for their extensibility where appropriate. The topics covered in this article include:

• Using the Windows Azure Diagnostics trace listener
• Performing an on-demand transfer
• Implementing custom logging
• Accessing data persisted to Windows Azure Storage
• Using the Windows Azure Platform
• PowerShell cmdlets to configure Windows Azure Diagnostics

Windows Azure Diagnostics: Initializing the Configuration and Using a Configuration File

The default configuration for Windows Azure Diagnostics captures some data but does not persist it. Consequently, the diagnostics configuration should be modified at role startup. In this article by Neil Mackenzie, author of Microsoft Windows Azure Development Cookbook, the Initializing the configuration of Windows Azure Diagnostics recipe, shows us how to do this programmatically, which is the normal way to do it. In the Using a configuration file with Windows Azure Diagnostics recipe, we see how to use a configuration file to do this, which is necessary in a VM role.