MSBuild fail for beta 3

I'm trying out the beta version of NCover. I tried using my existing MSBuild project file, and it failed.

The UsingTasks failed because it was unable to locate the NCover task. I changed from TaskName from NCoverExplorer.MSBuildTasks.* to NCover.MSBuildTasks as this is the actual namespace for the tasks. The sample still refers to NCoverExplorer namespace.

When running MSBuild again, I get the following error;

Registered to Customer #: xxx NCover Enterprise Edition (1 User)

Command: "C:\Documents and Settings\bs\Lokale innstillinger\Temp\tmp6C40.tmp. ncoversettings" Command Args: Working Directory: Assemblies: (All Loaded Assemblies)

Program Output

Exception

-- Top-level exception (NCover.Utilities.Exceptions.ProfilerRuntimeException) The process could not be started. Ensure that it runs outside of NCover. -- Stack Trace at NCover.Framework.StartupProfiledProcess._StartProcess() at NCover.Framework.StartupProfiledProcess.Start() at NCover.Framework.ProfilerDriver.ExecuteNCover(Int32& profiledAppCode) at NCover.Framework.ProfilerDriver.Execute(Int32& profiledAppCode) at NCover.ConsoleMain.ConsoleMain.Main(String[] args) -- Inner exceptions The specified executable is not a valid Win32 application.

C:\Programfiler\MSBuild\Locus\TeamBuild.NCover.targets(19,3): error MSB6006: "NCover.Console.exe" exited with code 20000.

I have installed 3.0 beta x86

I have to say the exit codes are quite obscure, and so far I have been unable to find an exit code reference.

BjÃ¸rnar

RE: MSBuild fail for beta 3

Thank you for the feedback. The tasks were not completly finished when we launched Beta but we are working on finishing them and integrating them more tightly with NCover so they work smoothly and trouble-free. The documentation is one of the pieces we still need to update and improve.

We have been discussing the error code problem internally for some time. I have a question. When you recieve an error code from NCover, would you like to see a short description of the error before NCover exits? or is there a solution you would like better?

Stephen

RE: MSBuild fail for beta 3

A short error description would be great. I have only really used NCover using MSBuild tasks, and I need a short description on what is wrong, and how I can fix it. When integrated using MSBuild, an error code is not relevant, as most people have no idea what they mean.

We use TeamCity as our build server, and Log.Error/Fail is displayed on the main page of the failed build. To find other messages, we have to go through the build log to figure out what is going wrong, and most developers just report the problem to the configuration manager (me) to figure it out.

When integrating with TeamCity, there are some issues I have experienced (also reported in http://www.ncover.com/forum/show_topic/727). I first have to run the NUnit task for MSBuild/NAnt, and then I have to run NCover (which in turn also run NUnit). If not, no NUnit summary is reported on the main page for the build. Better integration with TeamCity would be nice, so the unit tests don't have to be executed twice.

I experience the following issues with error codes being reported: No/expired license: exit code 9000 (I think it was) Unit tests fail: exit code 1 from NUnit (? (the task is not actually informing me that one or more of the unit tests failed) The error reported in this thread: exit code 2000 Coverage not met: exit code 3

These are the ones I can remember. I've previously been using Clover.NET, and their MSBuild tasks also used the console commands to perform the work. The MSBuild (NAnt really) script then parsed the output on the console, and logged them to the output. Perhaps a way to do it for NCover as well?

Do you have a status for my previous posts? http://www.ncover.com/forum/show_topic/692 http://www.ncover.com/forum/show_topic/691

Best regards

BjÃ¸rnar

RE: MSBuild fail for beta 3

We are working on integration with several tools, among the many other things we do at the same time.

Post http://www.ncover.com/forum/show_topic/691 is logged, but will probably not be discussed internally until after the beta.

Post http://www.ncover.com/forum/show_topic/692 I am happy to report that we managed to squeeze this into the beta. NCoverExplorer.Console has been replaced by NCover.Reporting, and you'll want to look at the //mc argument. The help screen for it is fairly complete.