I started writing this as a general recap of PDC for team members but the more I thought about what was announced at PDC, the longer the email got. Ultimately I decided to put it out so you dear reader could also gain some insight from things announced at PDC.
For starters listen to the podcast we recorded with Scott Guthrie or “The Gu”, or “His Guness”, or “ScottGu” about Silverlight 4 announcements among other things while at PDC.
The big stories out of PDC that I think everyone should take note of are Silverlight 4, Entity Framework 4 and Windows Mobile. Wait Windows Mobile 7? Yes. Wait… I didn’t hear anything about Windows Mobile 7? Well I didn’t either and that is why this post is called “read between the lines”. Call it speculation or whatever, but I think I can bring you up to speed on what is about to happen (and no I have no official behind the scenes information, I’m just a guy with a brain). Before we get to Windows Mobile 7, let’s start with Silverlight.
Silverlight 4 had tons of announcements including:
- Camera and microphone support
- Trusted out of browser support. This means one can access COM (for example, an application could access Outlook APIs)
- Lots of line of business app controls
- Added support for drag and drop
- WCF RIA Services (this is basically what I’m calling the new CSLA, if you listen to the podcast you’ll find out that Rocky worked with the team closely on RIA Services)
- Print natively
Tim has a great recap of all the Silverlight announcements here with links to videos:
Let’s talk about Entity Framework 4.0 for a moment. This is another big piece of news. It is big because as .Net developers we will finally have one true way to access data that fits the multitude of ways we have to work. Here’s a recap of announcements (not a complete list, watch the videos from PDC):
- POCO – supports plain old clr objects
- EDM designer enhancements
- Better stored proc support
- Model first (then gen database model)
Doug Purdy (who we also interviewed for Deep Fried Bytes while at PDC) has a list of the sessions that cover the Entity Framework 4.0. Just start at the top and work your way down as far as you can. At least watch the first video as it shows off all the features of EF.
With the number of features that were announced in EF4 I think we are on the verge of seeing the demise of NHibernate usage by developers in the .Net stack. For those that have used NHibernate in the past, it is worth another look at the Entity Framework to be released in .Net 4.0. About the only thing EF4 doesn’t do that NHibernate does do is built-in caching (which hey, there’s this caching thing that AppFabric does, hmm, wonder if they’ll use that? Why not! ). But the big thing to note between EF4 and NHibernate is we are starting to see where this whole modeling thing with OSLO is going (edm files are m fles and so on). And of course there is the bigger picture of reusing this model in report services, BI and other areas (although we haven’t *seen* that really working yet, it is coming though see next sentence). As EF4 makes it way into other products throughout the Microsoft ecosystem it is going to be extremely hard to avoid the Entity Framework. Read between the lines, the writing is on the wall, LEARN THE ENTITY FRAMEWORK.
Just a side bar here because I know someone is going to ask me this at a later time. Will the Entity Framework kill NHibernate? Answer: Nope I’m not saying that.
Out of band developers that seem to have a knack for yelling the loudest will continue to use NHibernate but a much larger ecosystem will leverage the out of the box Entity Framework in .Net 4.0. Think back for just a bit. History is about to repeat itself all over again. Remember when we got MSTest and or MSBuild? Same thing is happening again. There is now an out of the box product for standardizing data access. Are their alternatives? Sure. Just as MSTest didn’t kill NUnit or MBUnit and MSBUILD didn’t kill NAnt, EF4 will not kill NHibernate. However, if you look at the number of developers using MSBuild or MSTest it is high. Extremely high. Why is that? Answer: pain, ease of use, integration, documentation. MSTest is not the best testing framework out there (this is a proven fact), but it is good enough for 90% plus test cases. Entity Framework 4.0 is going to put an ORM in the hands of developers. And you know what, it doesn’t suck either.
Windows Mobile 7
And now onto Windows Mobile 7.
Is this WinMo 7 above? I honestly don’t know, I found these screen shots on http://windowsphonemix.com/ web site. BTW, notice that URL? Mix? Yes Mix. Mix is the first of the three major conferences Microsoft puts on each year. The very last slide at PDC during the last keynote said, “Come to Mix 2010 for Windows Mobile 7 futures”. A lot of people missed this because they were tuned out from the SharePoint demos and already packing to leave. But there it was on the big screens. Thus we know Mix is when we’ll see Windows Mobile 7. Again, listen to the podcast to get some other insight.
Here’s a quote: “Three screens and the cloud”
We heard this over and over at PDC. Let’s read between the lines a bit shall we?
Now, let’s switch gears. What if I used Silverlight 4 to write my app? Well, it could work in the browser no doubt. Hmmm, it could also work on the Desktop using the out of browser experience with elevated permissions. What about mobile?
“Wait, didn’t you just say Keith that at Mix we’ll get to see Windows Mobile 7?”
“And hasn’t there already been talk of using Silverlight for mobile?”
“Aha! Three screens with Silverlight, I get it!”
That’s right my friendly .Net developers the writing is on the wall. The vision of WPF/e (WPF Everywhere) is about to come true. We’ve waited for years but it is just around the corner as I predicted would happen years ago.
(ok, so it wasn’t right around the corner but 3+ years later)
Moral of the story?
LEARN SILVERLIGHT so you can make millions of dollars building Mobile applications just like the iPhone devs. There, I just made you rich by putting this puzzle together for you, please send me 20% of all profits.
You are welcome.