If you are using WP, or are planning to use it, this version is a must-try. For more information of whats new and cool, have a look at the video.

Google has spent a lot of effort to make sure this version had all the original arcade game features. This includes the game crashing after the 255^th level, the hint of which direction they were going to turn by moving their eyes, etc.

For a game that’s 30 years old, it holds up remarkably well over time, and still has a hold on popular culture. Bring on the fun…

The most recommended way of implementing NOLOCK is to use a TransactionScope to affect the TransactionOptions associated with the commands of the LINQ context.

Heres a sample code :

using (new System.Transactions.TransactionScope(
	System.Transactions.TransactionScopeOption.Required,
	new System.Transactions.TransactionOptions
	{
		IsolationLevel = System.Transactions.IsolationLevel.ReadUncommitted
	}))
{
	// Retreive Data
}

partial class MyTargetContext {
     [Function(Name="NEWID", IsComposable=true)]
     public Guid Random()
     {
         throw new NotImplementedException();
     }
}

In the above example which returns a uniqe identifier (GUID), we are mapping the Random method to the NEWID SQL function. The IsComposable boolean property of the Function Attribute, defines if the method is mapped to a function (true) or to a Stored Procedure (false). Also note that since this method is mapped, the C# code is not executed.

We can call the above implementation as …

var posts = (from post in dbContext.Posts
			where post.IsActive && post.Category.Equals('Linq')
			order by dbContext.Random()
			select post).FirstOrDefault();

Although there are better alternative in terms of performance, this approach is much easier and should work fine for small / mid-size tables.

Here is a quick tip to increase the performance by disabling object tracking in LINQ using the ObjectTrackingEnabled property. This will turn off the unnecessary identity management of the objects.

using (NorthwindDataContext dbContext = new NorthwindDataContext())
{
	dbContext.ObjectTrackingEnabled = false;
}

The event also focuses on sharing videos and tutorials detailing the awesome features of jQuery 1.4. To ensure you don’t miss out on any of the goodies, subscribe to the email/rss feed or visit the site.

I have been using jQuery in most of my projects and am quite excited about the new release. Aren’t you?

The book contains the following chapters :

• Chapter 1: Welcome to Office 2010
• Chapter 2: Express Yourself Effectively and Efficiently
• Chapter 3: Collaborate in the Office and Around the World
• Chapter 4: Create and Share Compelling Documents with Word 2010
• Chapter 5: Create Smart Data Insights with Excel 2010
• Chapter 6: Manage Rich Communications with Outlook 2010
• Chapter 7: Produce Dynamic Presentations with PowerPoint 2010
• Chapter 8: Organize, Store, and Share Ideas with OneNote 2010
• Chapter 9: Collaborate Effectively with SharePoint Workspace 2010
• Chapter 10: Create Effective Marketing Materials with Publisher 2010
• Chapter 11: Make Sense of Your Data with Access 2010
• Chapter 12: Putting It All Together
• Chapter 13: Security in Office 2010
• Chapter 14: Training Made Easy

Download the eBook at http://cid-d7229b252a0ad6f2.skydrive.live.com/self.aspx/Public/First%20Look%20Microsoft%20Office%202010/693876ebook.pdf

var myVar = "This is a normal function...";

function ShowAlert(textToAlert)
{
	alert(textToAlert);
}

ShowAlert(myVar);

We all know that functions are also objects in JavaScript. Thus they can be evaluated using the eval() function and also in the case of setInterval() function you can pass the name of the function as an object. Thus like other objects, we can also use grouping operators like ( and ).

var myVar = "This is still a normal function...";

function ShowAlert(textToAlert)
{
	alert(textToAlert);
}

(ShowAlert)(myVar);

We are halfway there. Lets replace the name of the function with the function definition and make it a single statement.

var myVar = "This is a self-executing function...";

(function ShowAlert(textToAlert)
{
	alert(textToAlert);
})(myVar);

Ok. So far so good. Since we are going to run this function as soon as we create it, it doesn’t need a name. Next step is to make this function an anonymous function.

var myVar = "This is an anonymous self-executing function...";

(function (textToAlert)
{
	alert(textToAlert);
})(myVar);

And voila… We have created a self-executing anonymous function.

Although in this example, the advantage might not be obvious, but in real-world, this technique is quite helpful as it encapsulates the functionality and also prevents the cluttering of the global namespace. If you take a peek at the jQuery source code, you will notice that the whole library is wrapped in a single, self-executing function that is assigned to the jQuery global object. It’s precisely the reason that jQuery doesn’t pollute the global namespace nearly as much as other libraries.