msbuild - TFS Build Server "Can't find the valid AspnetCompilerPath" for TeamBuild publishing a Website -

i having problem tfs2013 using team build build publish of website.
works fine when publish web site dev machine using vs2013 , (right-click) publish web site option web site project. following error on tfs2013 build server:

c:\program files (x86)\msbuild\microsoft\visualstudio\v12.0\web\transform\microsoft.web.publishing.aspnetcompilemerge.targets(421,5): error :

**can't find valid aspnetcompilerpath** [c:\builds\3\web\development webdev\sources\web\website\development\asp.net\app\website.publishproj] done building project "c:\builds\3\web\development webdev\sources\web\website\development\asp.net\app\website.publishproj" (default targets) -- failed. 

**

i using follow msbuild arguments in team build setup.
/p:deployonbuild=true;visualstudioversion=12.0;deploytarget=webfilesystempublish;publishprofile=development

the development web transform works fine on build server in response 'publishprofile=development' argument. web.config file transformed our development environment. noted in msbuild argument, use filesystem publish option , want keep way.

i have modified build server 'c:\program files (x86)\msbuild\microsoft\visualstudio\v12.0\web\transform\microsoft.web.publishing.aspnetcompilemerge.targets' log properties follows in target 'configureforaspnetprecompilemerge':

<message text="[targetframeworkversion]: $(targetframeworkversion)" /> <message text="[aspnetcompilerpath]: $(aspnetcompilerpath)" /> <message text="[framework40dir]: $(framework40dir)" /> <message text="[msbuildtoolsroot]: $(msbuildtoolsroot)" /> <message text="[msbuildruntimeversion]: $(msbuildruntimeversion)" /> 

which logs following information website.log file team build: configureforaspnetprecompilemerge:

[targetframeworkversion]: v4.0 [aspnetcompilerpath]: [framework40dir]: c:\program files (x86)\msbuild\v4.0.30319 [msbuildtoolsroot]: c:\program files (x86)\msbuild\ [msbuildruntimeversion]: 4.0.30319

the [framework40dir] different local machine logging same data @ same msbuild target:

12> task parameter:text=[targetframeworkversion]: v4.0 12>
[targetframeworkversion]: v4.0 12> task parameter:text=[aspnetcompilerpath]: 12> [aspnetcompilerpath]: 12> task parameter:text=[framework40dir]: c:\windows\microsoft.net\framework\v4.0.30319 12> [framework40dir]: c:\windows\microsoft.net\framework\v4.0.30319 12> task parameter:text=[msbuildtoolsroot]: c:\program files (x86)\msbuild\ 12> [msbuildtoolsroot]: c:\program files (x86)\msbuild\ 12> task parameter:text=[msbuildframeworktoolsroot]: c:\windows\microsoft.net\framework\ 12>
[msbuildframeworktoolsroot]: c:\windows\microsoft.net\framework\ 12>
task parameter:text=[msbuildruntimeversion]: 4.0.30319 12>
[msbuildruntimeversion]: 4.0.30319

the teambuild value [framework40dir] is: 'c:\program files (x86)\msbuild\v4.0.30319' vs local dev machine of: c:\windows\microsoft.net\framework\v4.0.30319

this seems unusual.

i have changed teambuild file: 'c:\program files (x86)\msbuild\microsoft\visualstudio\v12.0\web\transform\microsoft.web.publishing.aspnetcompilemerge.targets' manually set property of framework40dir 'c:\windows\microsoft.net\framework\v4.0.30319' seems hang whole teambuild process when gets point , runs team build forever until manually stop it.

this same solution worked here: tfs build server cannot publish profile work: "can't find valid aspnetcompilerpath" doesn't work me. issue identical problem.

the build server date tfs2013.3. not have visual studio 2013 installed on machine , not that. have read vs not needed tfs team builds.

help issue appreciated.....thanks.

i install vs2013 onto build server removes majority of these issues, allows run code coverage against unit tests , doesn't require licence long have valid licence on development machine. know isn't answer wanted.