- The Beginning: Basics
- Designing for an Interface: Big Ideas
- Making the Most of Your Controls
- Stick to the [Framework] Basics
- How It Works
- Great Sources
Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
Stick to the [Framework] Basics
I prefer to use plain text files to store and retrieve project data. They’re easy to understand. I like XML, especially for data with many complex relationships. But for an attendance application, a simple text list of the absent students’ names is sufficient.
I decided to output the data simply. I’ll open files named with the date, write each absent student’s name, and then close the file.
More than two years ago, I wrote about the possibilities of fast coding with the My object. It’s a great way to code PC apps more quickly. However, the Compact Framework is a subset of the .NET Framework. Compact Framework designers kept the Framework compact by avoiding extra classes such as the My object. In fact, the key mantra for coding for CE and Pocket PC is this: Inherited doesn’t mean supported. Several interface elements don’t make sense with the size of the Pocket PC screen. For example, don’t expect fancy icons in your dialog boxes.
Code simply. Use core classes and avoid higher-level abstractions such as the My object. In fact, consider your possible Pocket PC implementation of most apps you build, especially utilities.