October 2007 - Posts
If you are using CAB and wonder about Acropolis or WPF Composite Client, you should read this post. If you are using Windows Forms and consider using WPF, you should read the post too.
Ward Bell writes a great follow-up to yesterday's announcement about the future of CAB, Acropolis, and WPF composite applications.
Back in June, Microsoft announced Acropolis. Now, the Acropolis team and the Patterns & Practices team announce new plans.
I haven't looked at Acropolis after July, and this new change of plans confirms that this was a wise decision. These days, I don't really have time to spend on moving targets like Acropolis was.
The Acropolis team announce that Acropolis enters a new phase. They "will begin to roll many of the Acropolis concepts into future versions of the .NET Framework for the desktop and Silverlight". Yet, no new previews are planned!
At the same time, the Patterns & Practices team announce that they will provide WPF Composite Client, "guidance (samples, applications blocks, patterns and so on) for building composite client applications for .NET Framework 3.5 and Visual Studio 2008". The target is to have all of the new guidance ship before the end of 2008. They plan to "develop several small deliverables that they will ship in a piecemeal fashion", but no dates set for these.
In the meantime, the official recommendation is to stick to CAB and SCSF, and use the Windows Forms and WPF interop if you need WPF in your composite applications.
For more information about the future of Acropolis and the WFP Composite Client, read the announcements on the Acropolis blog and on Glenn Blocks' blog.
This year, I'll be at TechEd Europe for the first time. It will be a good occasion to meet if you are there as well.
You'll be able to find me at the Ask The Experts (ATE) booths, where I'll probably be discussing about LINQ.
You should be able to spot me with an ATE shirt or a more customized t-shirt...
See you there... Follow the white t-shirt!
Cross-posted from http://linqinaction.net
The language specifications for the upcoming versions of the C# and VB.NET languages have been published by Microsoft.
The Word document for C# 3.0 contains no less than 519 pages. Something to keep you busy for the week-end...
The equivalent document for VB.NET 9.0 contains only 338 pages, but it's only a pre-version of the specification. The author, Paul Vick, lists what's in and what's out in this post.
Cross-posted from http://linqinaction.net
Dinesh Kulkarni, now ex-program manager on the LINQ to SQL project, gives on his blog a list of
what will not be included in the first version of LINQ to SQL. These are important restrictions to know if you haven't followed the story about LINQ to SQL so far and you plan to use it.
Cross-posted from http://linqinaction.net
Dinesh Kulkarni, program manager on the LINQ to SQL project, presents the logic behind LINQ to SQL's Attach() set of APIs. Attaching and detaching objects to and from a DataContext is something that seems to be a source of confusion, based on the questions in the forums. Attaching is a useful feature especially in multi-tiered system, which often involve stateless ASP.NET applications or web services. Dinesh explains when you need to attach objects and the various options.
Make sure you also read this post about the changes in Attach's behavior between Beta2 and RTM.
Cross-posted from http://linqinaction.net
More Posts