After
installing .NET framework 4.5 I started to experience build errors and warnings when building solutions containing projects targeting .NET 3.5 in Visual Studio 2010.
One of the warnings said:
The
primary reference "Dropit.Extension, Version=4.1.0.142, Culture=neutral,
PublicKeyToken=8fe83dea738b45b7, processorArchitecture=MSIL" could not be
resolved because it has an indirect dependency on the framework assembly
"System.Web.DataVisualization, Version=3.5.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35" which could not be resolved in the
currently targeted framework.
This
warning isn’t specific for the primary ref assembly mentioned above, it could
be any other assembly it seems.
After playing around with the .csproj-file trying to take control over MSBuild I discovered this workaround:
After playing around with the .csproj-file trying to take control over MSBuild I discovered this workaround:
- In VS, try to identify the referenced assembly or assemblies causing the warning and set the specific version to true in the properties pane.
- Unload the project that fails to build in Solution Explorer
- Right click the unavailable project and then Edit
- Find the ItemGroup and Reference elements of the concerned assemblies, in this case
<ItemGroup>
...
<Reference Include="Dropit.Extension, Version=4.1.0.142, Culture=neutral,
PublicKeyToken=8fe83dea738b45b7, processorArchitecture=MSIL">
<HintPath>..somepath\Dropit.Extension.dll</HintPath>
</Reference>
and add the SpecificVersion element
and add the SpecificVersion element
<ItemGroup>
...
<Reference Include="Dropit.Extension, Version=4.1.0.142, Culture=neutral,
PublicKeyToken=8fe83dea738b45b7, processorArchitecture=MSIL">
<HintPath>..somepath\Dropit.Extension.dll</HintPath>
<SpecificVersion>True</SpecificVersion>
</Reference>
6. Save and build - and it builds!
The service offers not only efficiency, binance sverige and transparency, customer support and a high level of security, which will effectively protect your account from possible attacks.
ReplyDelete