It's really a shame that I no longer trust the Windows Indexing results. IMO, the ENTIRE disk/system should be indexed, not just directories which are default and manually added. So many times I've searched for a filename to find no results but the file is there when I go spelunking with Explorer. Windows indexing is really an epic fail IMO.
Sorry, this is quite a disappointing presentation. The only WPF-related content were the XAML editor changes which were nice and the WPF per-window DPI changes. The rest was general VS discussion of things like edit and continue, debugger, managed memory analyzer, NuGet, another Azure sales pitch. Loopback with WinStore app? we're choosing WPF for a reason -- our customers have told us they do NOT want WinStore apps.
Don't forget, XAML is used in WPF and SL as well. It's a bit disappointing to call this a "XAML" project. I was excited to see some new WPF goodness. Alas, this is a Windows Store project which happens to use XAML.
Have to agree with some of the comments about the UI. If I had to use something like this daily I'd go nuts. Metro UI may be okay for music/news/games apps but something as simple as this starts to reveal the limitations of this UI language. There is just way too much functionality buried under rocks. The application loses it's discoverability in exchange for a barren UI.
"For better or for worse, desktop apps are desktop apps." -- this quote makes me sad. It says to me that no investment has been made to improve the desktop developer's life. As a scientific data visualization tool, our app has MANY windows (and needs all of them). We would LOVE to do XAML UI in C++ with our desktop app. A Windows Store app makes no sense at all for our app. What do we desktop devs have to look forward to? We use WPF now (from C++/CLI) but it's just too darn slow and uses .NET but only so that we can use WPF + XAML.