With MIX 2010 just barely a few hours behind us, I've decide to share my thoughts on the new WP7 from a development perspective of someone who has been writing iPhone apps for the last 6 months.
.NET RIA services is one of the new toolsets made available during MIX 2009. In this blog post I talk about what it is and why you should care (trust me, you'll care)
CLINQ v1.x had an implementation of the weak event pattern, but it was custom and difficult to maintain. CLINQ v2.0 uses the weak event pattern implementations that are available to all .NET developers. I discuss this pattern in this blog post.
I haven't said much about CLINQ lately but that's mostly because we've been trying to get v2.0 ready to ship. We're nearly there, so I thought I would start by talking about one of the new features - smart property notifications
With the PDC coming up shortly and Microsoft's trickled announcements of Visual Studio 2010 and the .NET Framework 4.0, what is Microsoft's direction, and will it work for them?
Lately the decision as to which mobile devices to target and which mobile SDK to use for building your application has become much less clear. This blog post takes a look at some of the current options for building mobile apps; their pros and cons
To someone in my position, who follows both Microsoft (.NET) news and Apple (Cocoa) news, the comparing and contrasting between MobileMe and Live Mesh as developer platforms is inevitable. Here's my first stab at a comparison
Recently a Microsoft developer posted a blog entry detailing a very negative experience he had with the iPhone SDK, Cocoa, and Xcode. MS developers allowing their first impression to taint their view of Mac programming is common, but easily corrected
It seems lately that the .NET Framework is gaining foothold everywhere, and the ability for developers to target multiple platforms with maximally reusable code is bigger than ever before
Someone posted in a comment on my WPF globalization post that they couldn't parse chinese numbers. I ran a quick code demo and sure enough, TryParse fails when trying to parse Japanese Kanji as well.
While everyone else is jumping up and down with joy, I've got mixed feelings about Microsoft releasing the source code to the .NET Framework, including ASP.NET, WPF, and WinForms
I've been working on some code where I needed to create an instance of a class at runtime based on the string name of the class. I knew how to do it in .NET, so I tried it out in Cocoa and I was pleasantly surprised.
Recently I decided that I wanted to see if creating new managed threads actually distributed my work across multiple cores and/or multiple processors. I was surprised by the results!
Having been a C# developer for more than 6 years, and starting to explore the world of Cocoa programming with Objective-C 2.0, I've discovered a fundamental difference in Developer Experience philosophy.
SharePoint developers have traditionally had huge difficulty in setting up development environments. There's good news and bad news - its easier with SharePoint 2007, but its still not perfect
So the other day I was thinking about how I was going to design the schema for the Ulysses Agenda game's server-side database, and then I had a revalation! I wanted pizza! But after I had that revalation, something else dawned on me!
