Using Microsoft.WindowsMobile

  • Thread starter Thread starter Thomas Freudenreich
  • Start date Start date
T

Thomas Freudenreich

Hello I'm using vs2008 und WM5 with .NET 3.5CF. Every time I include
Microsoft.WindowsMobile I got warnings like

Consider app.config remapping of assembly "System.Drawing, Culture=neutral,
PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from Version
"1.0.5000.0" [] to Version "2.0.0.0" [C:\Program
Files\Microsoft.NET\SDK\CompactFramework\v2.0\WindowsCE\System.Drawing.dll]
to solve conflict and get rid of warning.

Everybody can try to compile SmsIn from the samples Dir in the WM5 or 6
SDK. You will get the same warnings.
What should I wrote to the app.config? Is there any other solution, maybe a
download of WindowsMobile which is compiled aggainst 2.0 or 3.5 ?

Thomas
 
I just ignore those errors. The WindowsMobile namespace is based on CF 2.0.
However, 3.5 should run 2.0-based classes at least as well as 2.0 did, so
there's nothing to worry about unless something doesn't work.

Paul T.
 
Am Thu, 29 Oct 2009 11:49:01 -0700 schrieb Paul G. Tobey [eMVP]:
I just ignore those errors. The WindowsMobile namespace is based on CF 2.0.
However, 3.5 should run 2.0-based classes at least as well as 2.0 did, so
there's nothing to worry about unless something doesn't work.

Paul T.

Thomas Freudenreich said:
Hello I'm using vs2008 und WM5 with .NET 3.5CF. Every time I include
Microsoft.WindowsMobile I got warnings like

Consider app.config remapping of assembly "System.Drawing, Culture=neutral,
PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from Version
"1.0.5000.0" [] to Version "2.0.0.0" [C:\Program
Files\Microsoft.NET\SDK\CompactFramework\v2.0\WindowsCE\System.Drawing.dll]
to solve conflict and get rid of warning.

Everybody can try to compile SmsIn from the samples Dir in the WM5 or 6
SDK. You will get the same warnings.
What should I wrote to the app.config? Is there any other solution, maybe a
download of WindowsMobile which is compiled aggainst 2.0 or 3.5 ?

Thomas
.
Click to expand...
Click to expand...

Thanks. As long as this warnings are related to Microsoft.WindowsMobile I
will ignore them. But I read somewhere that you should'nt do that
generally, because sometime it can crash in the dest-platform. Is that
true?
Thomas
 
Sure. You always should read the warnings that the compiler generates.
Most errors of this format fall into two classes: this one, where there's
just a different base version for a module, and the case where someone
mistakenly references a desktop assembly from a smart device project, which
won't work.

Paul T.

Thomas Freudenreich said:
Am Thu, 29 Oct 2009 11:49:01 -0700 schrieb Paul G. Tobey [eMVP]:
I just ignore those errors. The WindowsMobile namespace is based on CF
2.0.
However, 3.5 should run 2.0-based classes at least as well as 2.0 did, so
there's nothing to worry about unless something doesn't work.

Paul T.

Thomas Freudenreich said:
Hello I'm using vs2008 und WM5 with .NET 3.5CF. Every time I include
Microsoft.WindowsMobile I got warnings like

Consider app.config remapping of assembly "System.Drawing,
Culture=neutral,
PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from Version
"1.0.5000.0" [] to Version "2.0.0.0" [C:\Program
Files\Microsoft.NET\SDK\CompactFramework\v2.0\WindowsCE\System.Drawing.dll]
to solve conflict and get rid of warning.

Everybody can try to compile SmsIn from the samples Dir in the WM5 or 6
SDK. You will get the same warnings.
What should I wrote to the app.config? Is there any other solution,
maybe a
download of WindowsMobile which is compiled aggainst 2.0 or 3.5 ?

Thomas
.
Click to expand...
Click to expand...

Thanks. As long as this warnings are related to Microsoft.WindowsMobile I
will ignore them. But I read somewhere that you should'nt do that
generally, because sometime it can crash in the dest-platform. Is that
true?
Thomas
Click to expand...
 
Back
Top