Configuration File Confusion in .NET Compact Framework 2.0

I've been seeing a lot of conversations lately regarding the status of Configuration File support in .NET CF 2.0 - it seems like maybe a clear word on .NET CF 2.0 Configuration File support might be in order. J

You'll recall from my post Running .NET Compact Framework 1.0 Applications with the .NET Compact Framework 2.0 Runtime a few weeks ago that you can use a Configuration File to control which version of the .NET Compact Framework Runtime your application runs in. Unfortunately, the addition of Runtime version control with Configuration Files does not equal Configuration File support.

Although, .NET CF 2.0 does include Configuration File support for Runtime control, it does not provide application-based Configuration File support. Basically none of the classes in the System.Configuration namespace are provided.

So what to do? Like in so many other cases, its OpenNETCF.org to the rescue.

Their OpenNETCF.Configuration namespace provides just about everything you'll need to use Configuration Files within your application. The OpenNETCF.Configuration namespace is Class name and Member name compatible with the Full .NET Framework's System.Configuration namespace so your existing knowledge of Configuration File programming makes the OpenNETCF classes immediately useful.