View
244
Download
0
Category
Tags:
Preview:
Citation preview
1
.NET Compact Framework 2.0 and
OpenNETCF Smart Device Framework 2.0
Chris TackeOpenNETCF Consultingwww.OpenNETCF.com ctacke@opennetcf.com
2
Goals
• Overview of CF2.0 and SDF2.0• What’s new in CF 2.0 and SDF 2.0• Why use the .NET CF 2.0 and SDF 2.0• Who’s using the CF and SDF• Get you excited about mobile development
3
Compact Framework Overview
• Gives developers the ability to develop for mobile devices
• Compact Framework Availability● 1.0 – Visual Studio 2003 Professional● 2.0 – Visual Studio 2005 Standard Edition
• CF 2.0 can target Windows Mobile 2003+• Develop using C# and VB.NET• Great opportunities but CF 1.0 had a few shortfalls
4
What’s New in CF 2.0
• Anonymous Methods• Generics• GUI Improvements • Enhanced Native Interop• *Cryptographic Support• Messaging Queue (MSMQ)• *Registry Keys• *Serial Ports• Better Xml Support• New device only classes available• *Improved threading support
this.textBox1.TextChanged += delegate(object sender, EventArgs e){ MessageBox.Show("Text changed for " + ((TextBox)sender).Text);};
X.509 certificates
Hashing: MD5 and SHA1
Symmetric key encryption: RC2, RC4, 3DES, DES
Asymmetric key encryption: RSA, DSA
*Available SDF 1.4
Microsoft.WindowsCE
*Notification
HardwareButtons
*ScreenOrientation
System.Windows.Forms
*ClipBoard
*DateTimePicker
*MonthCalendar
*WebBrowser
5
History of OpenNETCF and the SDF
• Started back in 2002 when Beta 1 of Smart Device Extensions (pre-CF1.0) released by Microsoft
• Grass roots was from Compact Framework newsgroups
• Collectively started dumping code on one website• Code converted and organized in the Smart
Device Framework• SDF 1.0 released September 2003
6
What’s New in SDF 2.0
• OpenNETCF.Net.FTP• OpenNETCF.Drawing.Imaging• OpenNETCF.WindowsCE.DeviceManagement• OpenNETCF.RSS• OpenNETCF.CRC• OpenNETCF.Media.SoundPlayer• OpenNETCF.Phone
7
MSN Search Mobile
8
Mobile Image Viewer
9
Mobile Voice Notes
10
NetUI
11
Why Use .NET CF & SDF: Unscientific Experiment
Requirement: Application needs to notify user when the battery is at 25% of life remaining.
Developer with no SDF:
5.5 Hours
Developer with SDF:
2 hours
Difference of 3.5 hours in development time
12
Why Use .NET CF and SDF
Total Lines of Code: 48,564
Total Comment Lines: 24,240
Total Namespaces: 43
Total Classes: 415
Total Enums: 141
Total Methods: 3,609
Total Properties: 1,833
Total Events: 448
Total Interfaces: 21
Approximate development time: 8.5 man-years
13
Why Use the .NET CF and SDF
• Free to develop, free to deploy
• Award winning software two years in a row
• Visual Studio 2005 integration● Help● Project Templates
• Don’t have to re-invent the wheel
• Save countless hours in development
• No comparable products out there in the same space
14
Who’s using .NET CF and SDF• Cordless phone, DSL Modem, WIFI router• PIM, call logs, weather, movies +++
www.verizon.com/verizon-one
15
Who’s using .NET CF and SDF
16
Who’s using .NET CF and SDF
• Crop record management system for agriculture
www.mapshots.com
17
Who’s using .NET CF and SDF• We dogfood our own products
www.OpenNETCF.com
18
Who’s using .NET CF and SDF
• Sycada provides mobile field service solutions to a range of industries and services organizations
www.sycada.com
19
Who’s using .NET CF and SDF
• Mobile application for rail yard inspectors and repair crew
www.expressyard.com
20
Who’s using .NET CF and SDF
• Integrated solution for real-time and store-and-forward wireless medical data capture and data analysis systems
www.ebiostats.com
21
Who’s using .NET CF and SDF
• HTML Editor for Windows Mobile
www.isquaredsoftware.com
22
MEDC 2007The Connected Community – 5/1/07
Visit medc2006.com for an overview of last year’s event.
23
Contact Information
• E-mail: ctacke@opennetcf.com
• Website:● www.opennetcf.com● Blog.opennetcf.org/ctacke
© 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it
should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
Recommended