G
Guest
Folks,
I have a Smartphone Solution with two Projects:
1) Common
References, among others System and System.Windows.Forms
2) Foobar
References, among others: Common, System, and System.Windows.Forms
The Common Project compiles with no warnings.
Foobar, on the other hand, compiles with the following warnings:
Consider app.config remapping of assembly "System.Windows.Forms,
Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from
Version "1.0.5000.0" [] to Version "2.0.0.0" [C:\Program Files\Microsoft
Visual Studio
8\SmartDevices\SDK\CompactFramework\2.0\v2.0\WindowsCE\System.Windows.Forms.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 Visual Studio
8\SmartDevices\SDK\CompactFramework\2.0\v2.0\WindowsCE\System.dll] to solve
conflict and get rid of warning.
Each Project is referencing EXACTLY THE SAME DLL (V2.0.0.0). Nothing is
referencing V1.0.5000.0 DLLS.
In an attempt to fix this, I created new Projects, added the items from the
original Projects, re-added the References, and then removed the original
Projects from the Solution. The first time I built the Solution there were
no problems. Subsequent builds throw the error message.
In another attempt to fix this, I created a foobar.exe.config and added this:
<assemblyBinding>
<dependentAssembly>
<assemblyIdentity name="System.Windows.Forms" Culture="neutral"
PublicKeyToken="969db8053d3322ac" Retargetable="Yes" />
<bindingRedirect oldVersion="1.0.5000.0" newVersion="2.0.0.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System" Culture="neutral"
PublicKeyToken="969db8053d3322ac" Retargetable="Yes" />
<bindingRedirect oldVersion="1.0.5000.0" newVersion="2.0.0.0" />
</dependentAssembly>
</assemblyBinding>
This has no affect on the build; the error messages remain.
I am at a total loss. Any suggestions are gratefully appreciated. Thanks.
Joel Finkel
(e-mail address removed)
I have a Smartphone Solution with two Projects:
1) Common
References, among others System and System.Windows.Forms
2) Foobar
References, among others: Common, System, and System.Windows.Forms
The Common Project compiles with no warnings.
Foobar, on the other hand, compiles with the following warnings:
Consider app.config remapping of assembly "System.Windows.Forms,
Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from
Version "1.0.5000.0" [] to Version "2.0.0.0" [C:\Program Files\Microsoft
Visual Studio
8\SmartDevices\SDK\CompactFramework\2.0\v2.0\WindowsCE\System.Windows.Forms.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 Visual Studio
8\SmartDevices\SDK\CompactFramework\2.0\v2.0\WindowsCE\System.dll] to solve
conflict and get rid of warning.
Each Project is referencing EXACTLY THE SAME DLL (V2.0.0.0). Nothing is
referencing V1.0.5000.0 DLLS.
In an attempt to fix this, I created new Projects, added the items from the
original Projects, re-added the References, and then removed the original
Projects from the Solution. The first time I built the Solution there were
no problems. Subsequent builds throw the error message.
In another attempt to fix this, I created a foobar.exe.config and added this:
<assemblyBinding>
<dependentAssembly>
<assemblyIdentity name="System.Windows.Forms" Culture="neutral"
PublicKeyToken="969db8053d3322ac" Retargetable="Yes" />
<bindingRedirect oldVersion="1.0.5000.0" newVersion="2.0.0.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System" Culture="neutral"
PublicKeyToken="969db8053d3322ac" Retargetable="Yes" />
<bindingRedirect oldVersion="1.0.5000.0" newVersion="2.0.0.0" />
</dependentAssembly>
</assemblyBinding>
This has no affect on the build; the error messages remain.
I am at a total loss. Any suggestions are gratefully appreciated. Thanks.
Joel Finkel
(e-mail address removed)