Errors running MSBuild after targeting the 4.5.1 framework - Websites not building.

Question

What I'm trying to do;
Update a lot of projects in a solution because a necessary .dll now targets the .NET 4.5.1 framework and is used by several of my projects in my solution
Platform;
My Machine;
MicroSoft Visual Studio Ultimate 2013
v.12.0.21005.1 REL
Micorsoft .NET Framework
Version 4.5.51641
Build Server is the same.  That is a Windows Server 2012 R2
The problem;
When I check in the code (which builds and runs fine on my machine) and run my MSBuild project I get the following;
1) LOTS of messages when the websites try to build (the other projects build fine)
warning MSB3275: The primary reference "c:\...\SearchEngineServices.dll" could not be resolved because it has an indirect dependency on the assembly "DB, Version=1.0.809.1, Culture=neutral, PublicKeyToken=null" which was built against the
".NETFramework,Version=v4.5.1" framework. This is a higher version than the currently targeted framework ".NETFramework,Version=v3.5".
warning MSB3258: The primary reference "c:\...\SearchEngineServices.dll" could not be resolved because it has an indirect dependency on the .NET Framework assembly "System.Web.RegularExpressions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
which has a higher version "4.0.0.0" than the version "2.0.0.0" in the current target framework.
warning MSB3268: The primary reference "c:\...\SearchEngineServices.dll" could not be resolved because it has an indirect dependency on the framework assembly "System.Xaml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
which could not be resolved in the currently targeted framework. ".NETFramework,Version=v3.5". To resolve this problem, either remove the reference "c:\...\SearchEngineServices.dll" or retarget your application to a framework version which
contains "System.Xaml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089".
(I just grabbed a few to include all of the MSB warning numbers - there are hundreds of these messages)
2) This message...
C:\Windows\Microsoft.NET\Framework64\v2.0.50727\aspnet_compiler.exe -v /LITWebServices -p LITWebServices\ -u -f "c:\mileg\tfs\build\MILeg\MILegNightlyReleaseBuild\bin\Mixed Platforms\Release\_PublishedWebsites\LITWebServices\\" 
That v2.0.50727 seems wrong!
3) this message...
c:\mileg\tfs\build\MILeg\MILegNightlyReleaseBuild\src\LITWebServices\web.config(34): error ASPCONFIG: Unrecognized attribute 'targetFramework'. Note that attribute names are case-sensitive. [c:\mileg\tfs\build\MILeg\MILegNightlyReleaseBuild\src\LITWebServices.metaproj]
The 'targetFramework' tag was added to the LITWebservices project's web.config when I took the framework up to 4.5.1 but it's not recognized on the build server. 
These are some of the things I've tried;
goofing around with the MSBuild project I made the following changes... (I've cut a lot of stuff out of the build xml)
<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="DesktopBuild" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" ToolsVersion="4.0">
<==changed the ToolsVersion from 3.5 to 4.0
  <Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets"/>
  <ProjectExtensions>
    <BuildMachine>devmileg</BuildMachine>
  </ProjectExtensions>
  <PropertyGroup>
    <ProductVersion>10.0.11107</ProductVersion> <==Added this ProductVersion tag
    <TargetFrameworkVersion>v4.0</TargetFrameworkVersion>
<==Added this TargetFrameworkVersion tag
    <TeamProject>MILeg</TeamProject>
    <BuildDirectoryPath>C:\mileg\tfs\build</BuildDirectoryPath>
    <DropLocation>\\devmileg\drop</DropLocation>
    <WorkItemFieldValues>Symptom=build break;Steps To Reproduce=Start the build using Team Build</WorkItemFieldValues>
    <UpdateAssociatedWorkItems>true</UpdateAssociatedWorkItems>
  </PropertyGroup>
  <ItemGroup>
    <SolutionToBuild Include="$(SolutionRoot)\MILeg.sln"/>
  </ItemGroup>
 </Project>
I think I need to fix the fact that the build is trying to run the aspnet_compiler.exe from the v2.0.50727 folder. C:\Windows\Microsoft.NET\Framework64\v2.0.50727\aspnet_compiler.exe
Do you think that is the main problem, and if so, How do I do that?  
Crazy question.  What would happen if I put the aspnet_compiler.exe from the v2.0 folder into the 4.0 folder?

Answer 1

Hello JJQuinn,
I don't recommend you do that since I'm not sure if there is any upgrade to this tool.
So I checked my 4.0 folder I can find the tool aspnet_compiler.exe and I compared the two files
As you can see, they are totally different. So I believe you will still get errors if you copy 2.0 version to 4.0 version.
I have this idea, if you still want to target to .NET 2.0 version, please enable .NET 3.5 on your OS. It seems it is not by default enabled on Server 2012 or Win 8.
If .NET 4.0 folder missed the aspnet_compiler.exe, you may need to fix .NET 4.0 first, try sfc /scannow to repair your OS and check whether the .NET 4.0 folder will have that file.
Best regards,
Barry
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.