dotnet compact framework: Porting from .NET Framework to .NET Compact Framework -- dotnet compact framework

Re: Porting from .NET Framework to .NET Compact Framework

ctacke/
7/27/2007 5:07:22 PM

dotnet compact framework: #3 is most certainly a license violation.

Search for Daniel Moth's blog - he's got loads of tips on writing code to
work on both.

--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Managed Code in an Embedded World
www.OpenNETCF.com

[quoted text, click to view]

Porting from .NET Framework to .NET Compact Framework

Susumu
7/27/2007 7:44:40 PM

I am attempting to port a C# library written under .NET Framework 3.0
to .NET Compact Framework 2.0, and am running into several issues
where I am not sure how to proceed.

As there are a number of classes that the library references that are
not in the Compact Framework, I have been taking the following three
approaches (in order of priority): 1) attempt to remove the dependency
altogether by stripping out functionality, 2) re-implement the
functionality offered by the Framework class using only CF classes,
and 3) manually pulling in Framework class definitions (using Rotor's
Reflector) and including it in my project.

When I have to resort to 3), I've come across a number of class
definitions that make use of attributes that do not exist in .NET CF,
such as SecurityPermissionAttribute and ReliabilityContractAttribute.
I'm not too familiar with exactly how these attributes are used, but
since these don't exist in .NET CF, would it be safe to simply comment
them out?

Also, when I used Reflector to look into
System.Collections.Generic.SortedDictionary, it generated a number of
lines that fail to compile, such as:

if (base.valueComparer.Equals(node.Item.Value,
base.<>8__locals4.value))

I've never seen such syntax, is this a limitation of Reflector? Has
anyone ported SortedDictionary functionality to CF? (I suppose it
wouldn't be too bad to reimplement but it would be nice if something
already exists).

Thank you!

Susumu