As operating systems evolve so too must the applications that run on them, but at the same time, the new OS must support the applications that ran well on previous versions.
If you're a developer, then you know the drill: You get your app to run on OS A, then we come up with OS B and you need to do work to make your app run on OS B. Of course, the Windows team spends a great deal of time writing code to make it as easy as possible for
you to transition your app from OS A to OS B without having you rewrite your app...
Sometimes your app just works (no code changes on your part), sometimes you have to tweak a tiny bit of code, sometimes you have to make a fair amount of changes to your code, and sometimes you are left scratching your head wondering how in the world you're
going to get your app to run on the new platform.
Well, meet Doug Wood, Maarten Van De Bospoort, Vineet Sarda, and Pat Altimore. These are some of the folks who spend their time ensuring you don't have to pull your hair out to get your app running on our new OS offerings.
Here we talk about the most common gotchas in XP to Vista app migration, dig into the compatibility problem space in general, and address developer concerns when it comes to making their code run successfully on our latest general purpose operating system.
Tune in. Learn.
Check out Vineet's C9 Screencast covering session 0 isolation of services in Windows Vista
and what to look out for if you are a services developer...