← All articles
development

NCover Hangs on Configuring Profiler…

NCover 1.5.8 hangs at Configuring Profiler on a large 53-project solution. The fix: switch to a licensed NCover 2 build for your CI server.

Donn Felker

Donn Felker

2009.04.22 · 1 min read · updated July 5, 2013

Our main build broke today. We have about 53 projects in our solution (yes, its huge) and all of a sudden … pow … NAnt started timing out. Upon further investigation I noticed that the build was timing out at the following instance:

Coverage Log: Coverage.Log
Waiting for profiled application to connect…Connected
Configuring Profiler…

It would hang until I killed it or until NAnt timed out (600 seconds/10 Mins). If I killed it, I received an “Object not set to an instance of object” exception.

Digging around some more I found out that others had this very same problem.

Just as they were, I was using NCover 1.5.8, the last free version. I followed suit as them, and used our NCover 2 license for our build server and everything started working again.

It seems that NCover has a critical mass that it reaches and then its like a game of Tumba. It could only handle so much and then it just fell over.

If you’re having this issue, just run NCover 2.

Donn Felker

Written by Donn Felker

I've spent 25+ years shipping software, writing books, and running my own companies. I write about thinking clearly, working for yourself, and doing real work while AI rewrites the rules. New essays land here every week.

Get the newsletter

Keep reading