Using windows application project on a mobile device

Hello,

for a C# windows application I have created a project that is a kind of data
caching layer between the GUI and the remote server.
I am using socket operations for communication to server and a typed dataset
to cache the data.

Now I want to reuse that project as it is for a mobile application (e.g.
Windows mobile 5.0). SO I have created a new project in VS2008 for mobile
devices and added all files of my existing application project.

When I try to compile it there are hundreds of errors conserning the
dataset. It mainly complaints about "System.Runtime.Seriazable" and other
things:

.....
Error 51 The type or namespace name 'Serialization' does not exist in the
namespace 'System.Runtime' (are you missing an assembly reference?)
C:\Dokumente und Einstellungen\Test\Eigene Dateien\Visual Studio
2008\Projects\SmartDeviceProject1\SmartDeviceProject1\DataSetMonitoring.designer.cs
9517 69 SmartDeviceProject1
Error 52 The type or namespace name 'Serialization' does not exist in the
namespace 'System.Runtime' (are you missing an assembly reference?)
C:\Dokumente und Einstellungen\Test\Eigene Dateien\Visual Studio
2008\Projects\SmartDeviceProject1\SmartDeviceProject1\DataSetMonitoring.designer.cs
9517 130 SmartDeviceProject1
Error 53 The type or namespace name 'Serialization' does not exist in the
namespace 'System.Runtime' (are you missing an assembly reference?)
C:\Dokumente und Einstellungen\Test\Eigene Dateien\Visual Studio
2008\Projects\SmartDeviceProject1\SmartDeviceProject1\DataSetMonitoring.designer.cs
93 60 SmartDeviceProject1
Error 54 The type or namespace name 'Serialization' does not exist in the
namespace 'System.Runtime' (are you missing an assembly reference?)
C:\Dokumente und Einstellungen\Test\Eigene Dateien\Visual Studio
2008\Projects\SmartDeviceProject1\SmartDeviceProject1\DataSetMonitoring.designer.cs
93 121 SmartDeviceProject1
Error 55 The type or namespace name 'Browsable' does not exist in the
namespace 'System.ComponentModel' (are you missing an assembly reference?)
C:\Dokumente und Einstellungen\Test\Eigene Dateien\Visual Studio
2008\Projects\SmartDeviceProject1\SmartDeviceProject1\DataSetMonitoring.designer.cs
203 40 SmartDeviceProject1
Error 56 The type or namespace name 'BrowsableAttribute' does not exist in
the namespace 'System.ComponentModel' (are you missing an assembly
reference?) C:\Dokumente und Einstellungen\Test\Eigene Dateien\Visual Studio
2008\Projects\SmartDeviceProject1\SmartDeviceProject1\DataSetMonitoring.designer.cs
203 40 SmartDeviceProject1
Error 57 The type or namespace name 'DesignerSerializationVisibility' does
not exist in the namespace 'System.ComponentModel' (are you missing an
assembly reference?) C:\Dokumente und Einstellungen\Test\Eigene
Dateien\Visual Studio
2008\Projects\SmartDeviceProject1\SmartDeviceProject1\DataSetMonitoring.designer.cs
204 40 SmartDeviceProject1
Error 58 The type or namespace name
'DesignerSerializationVisibilityAttribute' does not exist in the namespace
'System.ComponentModel' (are you missing an assembly reference?)
C:\Dokumente und Einstellungen\Test\Eigene Dateien\Visual Studio
2008\Projects\SmartDeviceProject1\SmartDeviceProject1\DataSetMonitoring.designer.cs
204 40 SmartDeviceProject1
....


Is there an easy way to transfer applications, or assemblys or classes or
entire projects into a SmartDevice application? Kind of converter? Why seems
the dataset to be completely different on both target plattforms? I would
have expected that things like the dataset is exactly the same with both
frameworks...


Thanks for your advice!

Hi Tom,

"Tom Berger" <BergersWorld2344@hotmail.com> wrote in message
news:OmNOm3FoIHA.3652@TK2MSFTNGP03.phx.gbl...
> When I try to compile it there are hundreds of errors conserning the
> dataset. It mainly complaints about "System.Runtime.Seriazable" and other
> things:

Binary Serialization isn't supported out of the box by the .NET Compact
Framework. If your application relies heavily upon this feature you may need
to investigate one of the third party serialization libraries which aim to
re-introduce this feature.

> Why seems the dataset to be completely different on both target
> plattforms? I would have expected that things like the dataset is
> exactly the same with both frameworks...

Most of the dataset functionality is the same between both platforms.
However some features, and in particular some of the method overloads are
not present on the .NET CF implementation as a way to reduce the size of the
runtime

One feature which is quite different between the two platforms is the
handling of design time attributes such as BrowsableAttribute and
DesignerSerializationVisibilityAttribute. The easiest way in your case to
resolve these compiler errors is probably to get Visual Studio to regenerate
the dataset designer code behind file. This will cause it to be regenerated
into a form where the generated code doesn't make use of features not
present on the .NET Compact Framework (but won't affect how the resultant
class can be used).

Hope this helps,
Christopher Fairbairn

Thanks Christopher!

> to get Visual Studio to regenerate the dataset designer code behind file
That is a very good idea... but how can I do that???
I simply added a new table or changed some column datatypes but the code
behind does not change.

Can you suggest a valid way of doing this?



"Christopher Fairbairn" <christopher@christec.co.nz> schrieb im Newsbeitrag
news:erIyqGHoIHA.2064@TK2MSFTNGP05.phx.gbl...
> Hi Tom,
>
> "Tom Berger" <BergersWorld2344@hotmail.com> wrote in message
> news:OmNOm3FoIHA.3652@TK2MSFTNGP03.phx.gbl...
>> When I try to compile it there are hundreds of errors conserning the
>> dataset. It mainly complaints about "System.Runtime.Seriazable" and other
>> things:
>
> Binary Serialization isn't supported out of the box by the .NET Compact
> Framework. If your application relies heavily upon this feature you may
> need to investigate one of the third party serialization libraries which
> aim to re-introduce this feature.
>
>> Why seems the dataset to be completely different on both target
>> plattforms? I would have expected that things like the dataset is
>> exactly the same with both frameworks...
>
> Most of the dataset functionality is the same between both platforms.
> However some features, and in particular some of the method overloads are
> not present on the .NET CF implementation as a way to reduce the size of
> the runtime
>
> One feature which is quite different between the two platforms is the
> handling of design time attributes such as BrowsableAttribute and
> DesignerSerializationVisibilityAttribute. The easiest way in your case to
> resolve these compiler errors is probably to get Visual Studio to
> regenerate the dataset designer code behind file. This will cause it to be
> regenerated into a form where the generated code doesn't make use of
> features not present on the .NET Compact Framework (but won't affect how
> the resultant class can be used).
>
> Hope this helps,
> Christopher Fairbairn
>