Visual Studio 2010 Beta is released. Late last year we had released a Community
Technology Preview (CTP) of VS2010. At that time I had written about some improvements
to the data binding improvements for WPF. The Beta has many more and we will discuss
them on this blog in a series of posts.
The experience is very similar to WinForms over DataSets. Let us take the example of
two tables: Customers and their Orders and create a form that lists the names of customers
and for each customer, their orders.
As described in my earlier post, we can add an EDM to our WPF project and have it
contain the two corresponding entities.
Here is how we can create the master details form:
1. From the tool box drag-drop a ListBox onto the form.
2. From the data sources window drag-drop the LastName column of Customer
entity onto the ListBox
3. Drag-drop the Order Entity from under the Customer node beside the ListBox on the
That’s it, really. You can press F5 to run the application and you will see your basic
master-details form working. The customers list box will show a list of customer names and
for the selected name the orders DataGrid will show their orders.
But note that the source for the CustomersViewSource__OMSEntities is the Customer
entity, where as the source for CustomersOrdersViewSource is the
CustomersViewSource__OMSEntities. Thus there is a master-details relationship between
the two CollectionViewSouce objects. Now customer list is bound to
CustomersViewSource__OMSEntities and the orders DataGrid is bound to
One more thing: We set the IsSynchronizedWithCurrentItem property of the customers list
box to True. That way every time you change the selection in the listbox the current item in
the CollectionViewSource is updated.
Second, if you look at the code behind the form, you will find that code to load the data for
the entities is generated in the form’s Loaded event handler. In this code we build the
object query for Customers and their orders, execute the query and assign the results to the
source property of the CollectionViewSource of the Customers entity.
Visual Studio Team System 2010 will include some pieces of Microsoft's "Oslo" modeling strategy, as first
demonstrated at Microsoft's TechEd conference earlier this year. The Architecture Explorer will allow architects and
developers to build, customize, and see an architectural diagram of an application and enforce architectural
consistency on builds of a piece of software. The software will support the Object Management Group's Unified
Modeling Language and domain-specific languages.
Other new features in Visual Studio Team System 2010 will include streamlined installation and configuration
processes, new features to encourage agile development techniques like including an Excel workbook that can hook
up to the back-end Team Foundation Server repository, and better build management.
There's no set date for release for Visual Studio 2010 or even a beta schedule, though the final release won't
necessarily come as late as the name implies. Microsoft will be folding together two formerly separate products,
Visual Studio Team Edition for Software Developers and Visual Studio Team Edition for Database Professionals, and
any customer who has either of those will get the other product for free with a Microsoft Developer Network
subscription when the new version comes around.
Microsoft intends to roll out its development plans in five stages. After talking about application life cycle
management, the next phase will be about improvements in the especially in Windows Workflow and Windows
Communication Foundation, which are two critical pieces of Microsoft's service-oriented architecture strategy. After
that, developers should expect more details about Visual Studio 2010 itself, how companies can build better
departmental apps with the next generation of Microsoft development software, and how the .NET Framework and
Visual Studio will "enable emerging trends" in software development.
The staged rollout flies in the face of a recent trend in Microsoft's developer division, that of extensive transparency
into future products. Unlike other groups like Windows, the developer division actively blogs about future products,
with tiny bits of new information constantly leaking out for those who seek it. However, Mendlen says, this strategy
has proved a bit overwhelming for some developers.
"Instead of gradually opening a fire hose of news, with this release we'll focus on individual themes," he said. "While
transparency is a good thing in many circumstances, the perception [among developers] was that they were getting
bombarded with information sort of constantly."