Base types, Collections, Diagnostics, IO, RegEx…
As many of you know at //build we announced that there will be a new .NET target framework for Metro style apps. To learn more about the goals of this new target framework I encourage you to watch Krzystzof Cwalina’s build talk "A .NET developer's view of Windows 8 app development".
One of the things we know people want to do is reuse existing .NET code but due to the constraints on Metro style apps it is not possible to directly reuse existing .NET class libraries nor is it always possible to simply recompile existing code. We realize this is going to be a pain point for many current .NET developers so we are working on a guide at the .NET for Metro style apps overview page which will assist developers in translating their existing .NET skill set into the Metro style apps world. Sometimes that means explaining why something was removed and other times it means giving another .NET or WinRT API to call instead. Today the page is limited but we are actively working on it internally to update it with more data for Beta and RTM.
For a demo of the kind of things you are likely to run into while porting code I suggest watching Daniel Plaisted’s build talk "Bringing existing managed code into Metro style apps".
While we are looking at many forms of feedback we would greatly appreciate any feedback on issues you run into while porting existing .NET code to Metro style apps. Please leave feedback in the comments or on the forums.
Feedback? Okay, here's some feeback: Metro looks like a nice Tablet UI, don't give a rate about it as a desktop app. I would NEVER use Metro to write a Windows app. If I want a Windows UI, I'd use Windows Forms, and otherwise I'd write a web app. Not sure why you're wasting everyone's time with this Metro stuff, other than as a way to try and convince the developers who make a living writing apps for Windows that they should now accept that their skills are so poorly valued by Microsoft that you think all they should be munging out are low-quality cheap fart apps like those so prevalent on the Apple walled garden.
Some of us actually write; you know; REAL applications with real requirements and real business needs that create real value. Metro is not a way of delivering this; and clearly Windows no longer is either. The reality is that all my future business applications will be delivered as HTML + JS targeting every device out there. Windows is now a commodity OS; courtesy of a Windows team that cannot deliver a consistent UI story.
Please, integrate Silverlight into IE instead of WinRT etc.
You mean well, but the mess you created can't be fixed.
Apple is so much better at protecting their developers investments. It is just sad.
Perfect comment. I second everything you said. Metro looks like a toy version of Windows. Good for slates, poor for real business users or power users. It works on a phone and maybe on touch devices. I think it should be left there.