Note that there are some explanatory texts on larger screens.

plurals
  1. POASP.NET MVC 1.0 AfterBuilding Views fails on TFS Build
    primarykey
    data
    text
    <p>I've upgraded from ASP.NET MVC Beta to 1.0 and did the following changes to the MVC project (as descibed in the RC release notes):</p> <pre><code>&lt;Project ...&gt; ... &lt;MvcBuildViews&gt;true&lt;/MvcBuildViews&gt; ... &lt;Target Name="AfterBuild" Condition="'$(MvcBuildViews)'=='true'"&gt; &lt;AspNetCompiler VirtualPath="temp" PhysicalPath="$(ProjectDir)\..\$(ProjectName)" /&gt; &lt;/Target&gt; ... &lt;/Project&gt; </code></pre> <p>While the build runs fine on our local dev boxes, it fails under TFS 2008 Build with "Could not load type 'xxx.MvcApplication'", see below build log:</p> <pre><code>... using "AspNetCompiler" task from assembly "Microsoft.Build.Tasks.v3.5, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a". Task "AspNetCompiler" Command: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_compiler.exe -v temp -p D:\Builds\xxx\Continuous\TeamBuild\Sources\UI\xxx.UI.Dashboard\\..\xxx.UI.Dashboard The "AspNetCompiler" task is using "aspnet_compiler.exe" from "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_compiler.exe". Utility to precompile an ASP.NET application Copyright (C) Microsoft Corporation. All rights reserved. /temp/global.asax(1): error ASPPARSE: Could not load type 'xxx.UI.Dashboard.MvcApplication'. The command exited with code 1. Done executing task "AspNetCompiler" -- FAILED. ... </code></pre> <p>MVC 1.0 is installed on TFS and the solution compiles when built within a Visual Studio instance on the same TFS server.</p> <p>How can I resolve this TFS Build issue?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload