Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    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.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. COI'll take a crack at this tonight and see how it works out. If I manages to get it working, I'll publish my exact steps related to TeamCity, for future reference. Initially when I read your post I was afraid I would then lose the ability to automatically run unit tests and code coverage as part of the build configuration in TeamCity, but switching to MSBuild doesn't remove those options. I think it did in an earlier version, perhaps that's why I haven't thought about experimenting more with MSBuild. Anyway, I'll test this. I suppose I need to ensure this only runs in TeamCity, and not locally.
      singulars
    2. COHaving visual studio or any other development application installed on a build agent can lead to lots of problems. You end up with assemblies in the GAC and other artifacts which would not normally be installed on a target environment. This results in tests passing on the build agent but your application fails on the target environment due to missing dependencies. If your build agent was clean this would be picked up earlier. Whilst there are always exceptions you should keep your build environment as clean as possible and keep everything relating to the build in source control.
      singulars
    3. COI'm aware of that problem. The way we solve this in our environment is through a clean 'build' agent which uses msbuild to compile. That machine runs all our tests as well. Building MSI's, using Code analysis is done on a different build agent with VS.NET during a later build step. That should catch most of the problems. As a final safeguard, you could have some simple automated smoke tests that use the release that comes from the last step. None of this would be needed if some of this essential functionality was in MSbuild rather than VS.NET. If it's still a major concern, change tools.
      singulars
 

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