Databases
StackOverflow2013
Postsdbo
POHow do I debug MSBuild Error MSB6006 from TeamCity?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow do I debug MSBuild Error MSB6006 from TeamCity?
    primarykey
    data
    text
    <p>So the scenario is that I'm trying to setup TeamCity to check out our ASP.NET solution from an SVN repository and compile it using a Release profile. The checkout from SVN works fine, however compiling the asp.net solution is where things start to fall apart.</p> <p>The first issue is that TeamCity seems almost bizarrely inconsistent when it comes to compiling. For instance, the first time it checks out the solution and compiles it, everything seems to work fine. However, if I force it to build after that then it gives: </p> <p>error MSB6006: "aspnet_compiler.exe" exited with code 1.</p> <p>and fails.</p> <p>I noticed that this only seemed to be happening on one of the projects in the solution. When I removed the project everything appeared to work fine. Since the above error is no help at all, I resorted to removing parts of the solution until I found the part that (seemingly) was causing the issue. </p> <p>Initially I was confident that I had identified the problem and so I cleaned everything up and tried to replicate the process from the start. I checked out a clean version and removed the 'problem pages' from the solution straight away. It didn't compile. So I'm scratching my head. It compiled before - why not now?</p> <p>Anyway by this stage I've burnt a significant amount of time trying to get this up and running. Since the project that it was complaining about was non-critical I just removed the whole thing. So Team City was once again happily building the remaining projects. I leave it alone and move onto the next thing.</p> <p>I come in the next day and do a force build - and it isn't compiling anymore. It's giving the same error as above but on a different project now!!!</p> <p>So I'm pulling my hair out trying to work out what's going on here. My questions are:</p> <ol> <li>Why does something that compiles fine in Visual Studio have so many problems in Team City?</li> <li>Why is the error given by MSBUILD so vague that it's practically useless (and is there any way to get something more useful)?</li> <li>Why does the solution build fine in Team City one day and not the next?</li> </ol>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USAdam Jones
    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.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. CODo you have any post-build events? Also, have you tried running msbuild from the command line on your local machine or on the build server, if so what is the outcome?
      singulars
      1. POHow do I debug MSBuild Error MSB6006 from TeamCity?
      1. USBrent Mannering
    2. COManagement has decided to go in another direction now so I'm no longer working on this. But to answer your questions - No, I don't have any post-build events and no, I haven't tried running msbuild direct from the command line. I am curious about this though so I'll give it go.
      singulars
      1. POHow do I debug MSBuild Error MSB6006 from TeamCity?
      1. USAdam Jones
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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