I just found out that when you call a method in a .NET class library FROM a Metro application, there's some kind of type conversion that happens seamlessly. However, if you call a method in a Metro/WinRT class library from a .NET application, this type conversion doesn't occur (except for primitive types, as far as I can tell). That means you can forget about calling any asynchronous methods from WinRT (and WinRT has a LOT of them) since the methods return a Task<T>. There's no type conversion from WinRT's version of System.Threading.Tasks.Task<T> and .NET's version of System.Threading.Tasks.Task<T>.
you just reference to System.Runtime.WindowsRuntime.dll then you can use await for WinRT async methods.
WinRT uses IAsyncOperation its not Task but it supports await pattern.
There is aloso AsyncInfoFactory class to convert a Task to IAsyncOperation stuff.
8 hours ago, Ian2 wrote
I guess there will be 2 hardware camps for some time to come (traditional PC and new style slate/touch devices) and I do have concerns that MS is trying to cover both with one product. (for most users this is going to result in a lot of confusion)
The actual release should maybe market the same product (Win8) targetted/focussed on the different hardware devices: Phone*, Slate, PC etc.)?
See I disagree that there as the industry moves forward that there are two distinct hardware camps. For example touch screen labtops, the ablity to dock devices such as tablets (and phones) calls for the ablity to support both tradional desktop apps and touch screen based apps.
Given that I was disapointed by the lack of information regarding the use of WinRt on the desktop and if there is any support for applications that present users both a metro based interface, and a wpf interface depending on the context the application is running in.
Watched the complete video and the ItemsControl metric is staggering. Charles this is one of the main reasons that WPF has been justifiably slaughtered as slow. Pretty much every data control i.e. listbox, treeview, datagrid, listview is an items control, in fact I had to renege to a winforms chart control in a recent project. This was a pretty significant bug, that affected the uptake of the platform, and why some of us keep asking for continued investment in the technology.
People complaining that WPF was slow were right
So, what do you think about what you've learned about the future of our platform (and are undoubtedly still learning given the sheer number ofsessions available from BUILD)?
It looks promising. More to review before knowing for sure. From what I've seen so far it looks like I may finally be able to avoid having an objective-c project and programmer on staff. It seems we may end up with a cohesive platform mix of cloud, desktop, server, and devices at both the OS and development level.
Have you had a chance to download the Developer Preview technologies?
No. Scott Hanselman says he installed it side by side with VS 2010 without issues ("so far"). In our environment we still have VS 2005 for Windows Mobile development so I can't risk it. A spare PC may become available shortly at which time I'll see what I can do.
Comment removed at user's request.
Comment removed at user's request.
@bystander: Great! (not the Blend 4 crash, though... Please report that. Do you have error info?)
I have installed the developer preview, watched a few of the BUILD sessions, and seem at a loss. Metro looks like it would be really good on a tablet, but it doesn't work so well on a PC with a mouse and keyboard.
I'm glad that I won't have to p-invoke crappy old Win32 functions from Metro. But I'm a little irritated at this carrot / stick game with metro / non-metro non-ie development scheme.
What I think would be really interesting is if, the Metro platform was given away for free. But it you wanted the classic windows part. Charge me $100. That way you could see massive up-take, right away.
I am frustrated by not having the capability to properly test apps created to utilise PC hardware sensor capabilities (due to a lack of hardware currently on the market!). I am presently developing an augmented reality app for Windows Phone (hopefully being submitted for ingestion later today) and I would very much like to build on it and release a version for Windows 8.
We need some kind of a developer program to facililtate this please.
Thanks for listening.
Running the dev preview in virtual box. Still getting to grips with a lot of it, ranging from basic stuff to complex scenarios. For instance, I wanted to change my user tile. From the various BUILD videos, I had gathered that you could use your pictures wherever they are: locally, on skydrive, on facebook, whatever. I only found a way to use local pictures. I also figured that Socialite would implement a contract to let another application use it to choose a picture, so I figured that I could use Socialite to set my user tile to a picture on Facebook, but the Share charm turned up nothing.
All in all I'm thinking that I'd really enjoy it on a tablet (I actually debated wether to buy one of those Dell swivelling-screen things to run the dev preview on so that I'd have a keyboard and mouse for Visual Studio and just swivel it to tablet mode for the full tablet experience) but decided against it for now. Not convinced by the mouse keyboard scenario just yet. There's too much stuff you have to go back to the desktop for, and then it's kind of a pain. It could grow on me, who knows.
Also lots of stuff isn't working. The news feed app doesn't do anything, the weather app doesn't do anything... hard to judge the user experience that way.
Edit: Damn this stupid forum software.
@JoshRoss: This is a developer preview (and an early developer preview enabling you to program Metro style apps: that's the point of this release - to give developers a chance to test drive a new programming model for applications running in a new UI paradigm).
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.