Presentation is loading. Please wait.

Presentation is loading. Please wait.

Windows 8 for Existing.NET Developers Tim Heuer Program Manager Windows Developer Experience Microsoft Corporation.

Similar presentations


Presentation on theme: "Windows 8 for Existing.NET Developers Tim Heuer Program Manager Windows Developer Experience Microsoft Corporation."— Presentation transcript:

1 Windows 8 for Existing.NET Developers Tim Heuer Program Manager Windows Developer Experience Microsoft Corporation

2 Some UI platforms I’ve worked on… Access/VBA Delphi VB3->6 (+ASP) “Cool” VB.NET Palm UI Windows Forms WAP ASP.NET (WebForms) SharePoint (WebParts) WAP Windows Forms SharePoint (WebParts) ASP.NET (WebForms) Windows Presentation Foundation (WPF) Silverlight Windows Phone Windows 8

3 The ones I liked… Access/VBA Delphi VB3->6 (+ASP) “Cool” VB.NET Palm UI Windows Forms WAP ASP.NET (WebForms) SharePoint (WebParts) WAP Windows Forms SharePoint (WebParts) ASP.NET (WebForms) Windows Presentation Foundation (WPF) Silverlight Windows Phone Windows 8

4 .NET

5

6 Windows 8

7 You already have the skills to build Windows 8 apps with C# and VB

8 Using the Windows Runtime feels natural and familiar from C# and Visual Basic

9 .NET Framework and WinRT .NET (and C# and Visual Basic) is alive and well  Windows Runtime (Windows.*) native APIs projected

10 [DllImport(“kernel32.dll”)]

11 The C# code you have to write today…

12 The C# code you get to write on Windows 8

13 .NET Framework and WinRT .NET (and C# and Visual Basic) is alive and well  Windows Runtime (Windows.*) native APIs projected  Can use C#/VB to create WinRT components  Async everywhere: await/async keywords are your friends  Reference assemblies for.NET Framework Core  Surface area specific for targeting Windows Runtime apps  Redundancy removed when matching WinRT API exists  Portable Class Library projects  Shared code at source and binary level  Great for framework developers when possible

14 Extension methods bridge the gap between Windows Runtime and managed code

15 Streams Code Sample FileOpenPicker picker = new FileOpenPicker(); picker.FileTypeFilter.Add("*"); StorageFile file = await picker.PickSingleFileAsync(); Windows.Storage.Streams.IInputStream inputStream = await file.OpenReadAsync(); System.IO.Stream stream = inputStream.AsStreamForRead(); System.IO.StreamReader reader = new StreamReader(stream); string contents = reader.ReadToEnd();

16 Understanding WinRT and Windows 8 for.NET Programmers Podcast with Immo Landwerth, PM on the.NET Framework team http://aka.ms/winrtnetfx

17 Development Patterns  Code-behind approaches  Simpler apps  Event-driven  Coupling UI to logic  Model-View-ViewModel (MVVM)  Separation of concerns  More easily testable (TDD)  Binding-driven  No Behavior support currently

18 demo

19 In Windows 8, your.NET skills extend to C++ and JavaScript developers!

20 You can build Windows Runtime components that project into C++ or JavaScript by following a few simple rules

21 Only the public types and members in your WinRT components need to follow these simple rules

22 API signatures must use only Windows Runtime types Structs can only have public data fields All types must be sealed (except XAML controls) Only supports system provided generic types

23 Visual Studio has built-in support for building Windows Runtime component projects using C#/VB

24 demo

25 Windows.UI.Xaml

26  Same XAML primitives  Optimized for touch experiences  New UI Controls, familiar XAML structure  GridView/ListView  SemanticZoom  AppBar  Animation Library  ThemeAnimations and Transitions  Extensibility  Large 3 rd party ecosystem still thriving

27 demo

28 Resources and Localization  Common resource APIs for WinRT  No strongly-typed class generation from resource file  Folder- or file-based convention  RESW == RESX in schema  Windows 8 only supports String resources  XAML leverages a ‘merge’ technique for markup  String- and file-based resources compiled into PRI  Visual Studio indexes all files for you

29 demo

30 Data for Apps  WCF endpoints  Add Service Reference still works!  OData  In RP: Ultimate only, future will be NuGet/standalone  Anonymous type binding  Local Storage  IsolatedStorage  Windows.Storage  ESE (Jet)  SQLite

31 demo

32 Summary and More…  You can use.NET for Apps and more  Consider Portable Libraries as a method for code- share targeting  Create WinRT components when desired/needed  You can leverage your XAML/.NET skills to be successful quickly in the Windows Store!

33 You already have the skills to build Windows 8 apps with C# and VB

34


Download ppt "Windows 8 for Existing.NET Developers Tim Heuer Program Manager Windows Developer Experience Microsoft Corporation."

Similar presentations


Ads by Google