views:

363

answers:

2

I'm running Team City Pro (v4.0.2 build 8222) for a VS2008 sln file.

Right now I'm facing a problem where autogenerated code for private accessors in a test project not being generated and causes compile errors by not being able to find those (autogenerated) classes.

The build runner is the default sln2008.

Any configuration need to be changed? I checked the VS build log, and it doesn't show any msbuild entry for the autogenerated classes. The DLL for the autogenerated classes are just there.

Note: I am aware that testing private methods are the best way to do unit testing.

A: 

AFAIK, TeamCity doesn't use msbuild utility to build solution. Don't you want to ask TeamCity developers?

vpolozov
Yes, it's not answered yet either:http://www.jetbrains.net/devnet/thread/281914
Adrian Godong
Could you post an example application?
vpolozov
A: 
Paul Alexander
It is currently running "sln2008" runner, and switching to "MSBuild" will remove the option of running NUnit tests.
Adrian Godong
Paul Alexander
And where do I add this snippet to? The sln file?
Adrian Godong
It's only a sample that shows how to call NUnit from an MSBuild script. You can put it in any project that you want. If you're going to be using TC to manage your builds it would be very beneficial to learn a bit of MSBuild.
Paul Alexander