Via Larkware (a little late I know but I'm really busy on a project at the moment)
Data Access Application Block for .NET CF
Hurrah! the first time I've seen these two things mentioned together and I'm excited!
- Compact Framework
- Application Block
Now I know the awesome OpenNetCF SDF is pretty much the uber application block for CF development but it feels like quite a monolithic entity - a better delivery of it would have been offering a more granular level of packaging and under the branding banner of "Application Blocks" (IMHO).
What's exciting about Application Blocks appearing on the CF is the feeling of consistency from the desktop platform which I feel is lacking. Obviously device limitations aside there will always be differences between the full and compact framework but building applications for a Windows Mobile device should be just as focused on the business portion of the application and not the plumbing stuff (and this is a double edged sword because one of the reasons I love CF programming is that there is still uncharted territory out there for you to write your own app block/utility methods).
Anyway, top marks to BusinessAnyplace and a gold star for using the moniker "Application Block" - nice work guys!
Update: Compact Framework Instrumenatation Application Block - check it out!
Overview
The "Compact Framework Instrumentation Library" (CFIL) is a combination of the following from Microsoft Patterns & Practices:
- Logging Application Block (LAB)
- Microsoft Instrumentation Framework (MIF)
- Exception Management Application Block (EMAB)
Because we are on a constrained device we will have cut back on a lot of the functionality from the above three items and combine them into one. Also, there are a few differences from the original Application Blocks.
- Desktop client to view the data on the device.
- Since the .Net Compact Framework is a subset of the full Framework, we will use OpenNETCF.org Smart Device Framework (SDF) to supplement missing functionality from the Compact Framework.
- Limitations in the Compact Framework (for example StackTrace) cause us to hardcode some values, such as the method name. With Version 2 of the Compact Framework this will no longer be necessary.
http://msdn.microsoft.com/smartclient/default.aspx?pull=/library/en-us/dnnetcomp/html/instnetcfapp.asp