I am getting some conflicts when building and wonder if they have
something to do with it. Here is part of the build output, how do I
"remap" the assembly?
No way to resolve conflict between "System, Version=1.0.5000.0,
Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes" and
"System, Version=1.0.5000.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089". Choosing "System, Version=1.0.5000.0,
Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes"
arbitrarily.
Consider app.config remapping of assembly "System.Xml, Culture=neutral,
PublicKeyToken=b77a5c561934e089" from Version "1.0.5000.0"
[C:\Windows\assembly\GAC\System.Xml\1.0.5000.0__b77a5c561934e089\System.Xml.dll]
to Version "2.0.0.0"
[C:\Windows\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll]
to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.Windows.Forms,
Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from
Version "1.0.5000.0" [] to Version "3.5.0.0" [C:\Program
Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\System.Windows.Forms.dll]
to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System, Culture=neutral,
PublicKeyToken=b77a5c561934e089" from Version "2.0.0.0" [] to Version
"2.0.0.0"
[C:\Windows\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll]
to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.Drawing,
Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from
Version "1.0.5000.0" [] to Version "3.5.0.0" [C:\Program
Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\System.Drawing.dll]
to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.Data, Culture=neutral,
PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from Version "2.0.0.0"
[] to Version "3.5.0.0" [C:\Program
Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\System.Data.dll]
to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System, Culture=neutral,
PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from Version "2.0.0.0"
[C:\Windows\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll]
to Version "3.5.0.0" [C:\Program
Files\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE\System.dll] to
solve conflict and get rid of warning.
C:\Windows\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets :
warning MSB3247: Found conflicts between different versions of the same
dependent assembly.
C:\PMMobile 3.5\Controls\Disclaimers.cs(10,7): warning CS0105: The using
directive for 'System.ComponentModel' appeared previously in this
namespace
C:\PMMobile 3.5\Classes\UserNotification.cs(296,75): warning CS0728:
Possibly incorrect assignment to local 'nt' which is the argument to a
using or lock statement. The Dispose call or unlocking will happen on the
original value of the local.
C:\PMMobile 3.5\OpenNetCF\MarshalEx.cs(33,3): warning CS3021:
'OpenNETCF.Runtime.InteropServices.MarshalEx' does not need a
CLSCompliant attribute because the assembly does not have a CLSCompliant
attribute
I didn't see any major change from 03 to 05 either. There's got to be an
environment problem. I've not seen a 5 minute build for any managed
project.
--
Chris Tacke, eMVP
Join the Embedded Developer Community
http://community.opennetcf.com
I am upgrading from vs2003 so I figured why upgrade to vs2005 and cf 2.0
when 3.5 was released. I will try it in vs2005 and see how long it
takes using it.
"<ctacke/>" <ctacke[at]opennetcf[dot]com> wrote in message
Yes I'm using it. No builds take no longer than Studio 05.
--
Chris Tacke, eMVP
Join the Embedded Developer Community
http://community.opennetcf.com
Just wondering if anyone else out there is using VS2008 and if so,
are you experiencing it taking extremely long to build your mobile
projects? It is taking upwards to 5 minutes for mine to build.