From this InfoWorld article...

In a related issue raised during the session, Microsoft's J.R. Arredondo, senior product manager for Microsoft Office, said the company sees its Popfly technology, for quick creation of applications such as mashups and widgets, as a model for the future. The Office business application strategy at its core is about bringing simplicity and usability to the masses, Arredondo said.

That last line is exactly what I like to hear!  Of course, it would be nice to see some meat around statements like that, but it is good to know that the "powers that be" are thinking the way I am, or at least appear to be.  Now the questions is, how long will it take to go from these broad brush statements to something that customers can actually see and use.  Under 24 months would be fantastic, but I am not counting on it. ;-(

Building WPF applications??? Check out the latest updates building composite WPF apps and what is going on with Acropolis by checking out posts by the Acropolis team and Glenn Bock.

Johan Lindfors asked the title question on an internal alias and I thought the responses were pretty good and worth sharing since I have not seen anything posted along these lines anywhere else.  While this shouldn't be construed as "official Microsoft guidance", I would say that the feedback shown below is from some pretty smart folks so probably not too far off the mark.

I thought North Central's very own Mike Benkovich had a great, concise answer to this question...

LINQ to SQL is targeted for Rapid Development – simple generated model that is limited to a 1:1 relationship between conceptual data model and physical objects in the database. Very clean XML representation of model design and code behind file that leverages partial classes to allow the extension of functionality. One limitation is that it because the model generates T-SQL it is limited to use against SQL Server. LINQ to SQL will be part of Orcas release.

LINQ to Entities is based on the ADO.NET Entity framework, which allows for more complex relationships between the conceptual model and the data store. Also it is able to target other dbms beyond SQL Server that have implemented a provider. It supports multiple inheritance models, as well as customization of the conceptual schema.

Chad Hower posted some good follow-up to Mike's reply...

"One limitation is that it because the model generates T-SQL it is limited to use against SQL Server. " But others can, and will make their own LINQ to Oracle, Firebird, MySQL (Yuck!) and so forth.

and

LINQ to SQL is for more direct access - think about it as a type safe way to do what you do with SQL today. Of course it can do quite a bit more - including many of the things datasets can do. LINQ to entities is more "enterprise" targetted and focuses on a greater seperation of the data, as well as dynamic futures in how you change your model and or DB.

and Mike chimed in one last time...

LINQ to SQL is the ORM tool, as opposed to the queryable-ness. There are already LINQ to Amazon, LINQ to Flickr, LINQ to SharePoint, LINQ to (insert here) out there, and this makes the technology pretty compelling. The language extensions of C# 3.0 and VB 9.0 make it easier to enumerate, filter, sort and process sets of data regardless of where they come from. The specific implementation technologies including the SQL, Entities and XML just make it that much easier to create and manage the target set of objects on which to iterate.

Great for reducing impedence mismatches by leveraging some syntactic sugar sprinkled into the expression holes...(I heard that this weekend at a code camp).

............................

Pretty good stuff that is worth having in your back pocket.  Link it up if you think its worth others knowing as well.

Some self training materials have been posted here that will help you ramp your knowledge on WPF and Expression Blend.  WPF is very slick and who wouldn't want to have some rad skillz using it!  Link about it or forward it on so the world can be a better place due to great UI design! ;-)

Denny is an arch evangelist in North Central District and has some good insights on incorporating new technology in general, and Silverlight in particular, into development environments.  Take a read and enjoy some good thinking from someone that has an excellent frame of reference. 

Chris writes up a great entry on the disservice Microsoft is doing to VB.NET developers.  Its a wonderfully thought out and passionate post that I'll be passing along internally just to make sure it gets the right level of visibility.

No big deal for existing Slickthought subscribers (all four of you - bit of a bounce following HDC). ;-)  But I decided to give the Feedburner thing a whirl.  Not sure what it buys me exactly except some more in depth stat tracking, but what the heck.  I'm a lemming in this arena so I'll follow the crowd.  If you are willing, you can switch your syndication feed over to http://feeds.feedburner.com/Slickthought so I can see all the "gooey syndication goodness" that is feedburner.  Believe or not, someone actually pays attention to stuff like that! ;-)

Yep, another great Heartland Developers Conference.  This year's HDC was bigger and better than ever.  Joe Olsen, Phillip Wolfe and crew put on a great show.  It was great to get back to Omaha and see some old friends, make a couple of new ones, and in general just get back to my old stomping grounds.  It's also extremely nice to get to hang with fellow Microsofties for a few days.  We hardly ever work together so its nice to just have dinner and talk with co-workers and teammates that you hardly ever get to see.

My presentation on LINQ went well and you can download the slides here.  You can get info on the Popfly Contest here.

The only thing I would change - need widely available sodas!!!! ;-)  I'm not a coffee drinker so that is a big deal to me! Otherwise, top notch.