I sometimes hang out with Kevin at Code Camps in the Virginia area, so I thought I would post this video of his perspective on Windows 7, Silverlight, and being an MVP.
Note: Cross posted from
KodefuGuru.
Permalink
Four new “How Do I” videos on Azure have been added to MSDN. Check them out!
Leverage Concurrency in Windows Azure Table Storage?
Windows Azure table storage is designed to support many users at the same time. In this session, you’ll learn how Windows Azure table storage supports concurrency, and you’ll learn a few strategies to help you deal with any concurrency violations.
Use Paging in Windows Azure Tables?
To improve application usability, many applications need to support viewing data page-by-page. In this screencast, you'll learn how Windows Azure table storage provides a built-in mechanism that allows you to efficiently page through query results.
Sync Between Devices and the Cloud with FeedSync?
Syncing the cloud and a growing world of devices is a fundamental need in today’s world. In this video, you will learn how to use FeedSync feeds to synchronize Live Framework data between a device and the cloud.
Get Started with the Messenger Web Toolkit?
Making your application sociable is easy. In this screencast, Chris Parker uses simple code to add instant messaging to his Web site. In minutes he connects his Web site to 320 million Instant Messenger (IM) users on PCs, Macs, mobile devices and Xbox 360. These efforts can help bring new users to his application and retain them for a longer period of time through the use of cool features like chat, presence, contacts and profile information.
Here’s an example of some bizarre code I’ve seen recently. I’ve changed the variable names, but this is what the developer was doing.
Customer customer = new Customer();
customer = customers[response.CustomerKey];
The first line is completely unnecessary. If you instantiate an object, then assign the object to another instance, the first instance sticks around and eventually gets collected. However, there’s no reference to it. You can never use that instance. Here’s how it should look.
Customer customer = customers[response.CustomerKey];
I would assume that it was dirty code that should have been cleaned before checking into version control, except for the fact the lines were adjacent. For the life of me, I don’t know why anyone would create an unnecessary instance. Any ideas?