Warning messages using the Microsoft.WindowsMobile.Status namespace

  • Thread starter Thread starter HardBap
  • Start date Start date
H

HardBap

Windows XP SP 2
VS 2005
Compact Framework 2.0
Windows Mobile 5.0 Pocket PC SDK

target device is Windows Mobile 5.0 device.

here is the code (simplified for brevity):


using Microsoft.WindowsMobile.Status;

..
..
..

public static Boolean Check()
{
SystemState s = new
SystemState(SystemProperty.ConnectionsCount);

if((Int32)s.CurrentValue == 0)
{
return false;
}
else
{
return true;
}
}


It compilies successfully but I get these warnings:

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.

Consider app.config remapping of assembly "System, 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.dll] to solve conflict and
get rid of warning.

C:\WINDOWS\Microsoft.NET\Framework
\v2.0.50727\Microsoft.Common.targets : warning MSB3247: Found
conflicts between different versions of the same dependent assembly.


Is there a version of the Microsoft.WindowsMobile.Status namespace for
runtime 2.0? ( I can see that Microsoft.WindowsMobile.DirectX targets
2.0 but the other Microsoft.WindowsMobile.* namespaces target ver 1.1
of the runtime)

Is modifying the app.config the only way to get rid of warnings?
 
It sounds like you have added CF1 System.Drawing and System to your list of
references. This could be because you upgraded your project from CF to CF2?

Try removing the System.Drawing and System assemblys and re-adding them.
 
Back
Top