Registration free COM - XCopy deployment

How about using: Registration free COM
all you should have to do is add a manifest file. Or just add the COM-object as a reference to your project, and set the isolated property to true, then VS will create the manifest file. And then it would be possible to use different versions of NCover side by side. I could install 1.5.5. and still run the official buildscript for the product using 1.5.4 :)

Re: Registration free COM - XCopy deployment

The problem with that approach specifically is the Windows XP restriction - still plenty of corporates out there using Windows 2000...

There is another approach however using the current user registry which does work fine on all platforms - this has been used by my NAnt/MSBuild tasks and is also in the upcoming NCover 1.5.7 release (there will be a //reg option from memory which will register/unregister on the fly). There is a limitation however that this approach does not work for services or IIS - for those you still need good old regsvr32.

So to summarise, your options are:

(1) use my NAnt/MSBuild tasks which will automatically register any NCover version

(2) use the NCover 1.5.7 with the //reg option when it comes out

(3) If you profile IIS or services, then include in your script a call to regsvr32 to register the coverlib.dll just before you run NCover.

Re: Registration free COM - XCopy deployment

I too need to xcopy deploy ncover.

Re: Registration free COM - XCopy deployment

Well, your options for xcopy deployment are listed above - lots of people do xcopy deploy it, the trick as stated on numerous threads is to remember that coverlib.dll is COM registered - either by including a call to regsvr32 in your script or using the NAnt/MSBuild tasks for NCover from my website.

Re: 1.5.4. NCover fails with: Unable to establish communications

The problem is still true with NCover 1.5.5.

I did some investigations and it seems that the CCoverageProfiler::Shutdown callback ist not called in any case. But still I can't figure out the root cause of this problem.

Has anybody similar problems?

ThomasD

Re: 1.5.4. NCover fails with: Unable to establish communications

Yes, I just encountered this issue today. Any word?

Re: 1.5.4. NCover fails with: Unable to establish communications

Yes, I have run into the issue too.

I am running an AMD Athlon X2 with 4 GB of memory with WindowsXP Pro with all the latest updates available. I have plenty of hard drive space (the location where my code is has nearly 260 GB available)

I am running .Net 1.1 applications. The timing is very inconsistent. If I run the exact same code on my office machine (the machine above is at home) I don't get the problem and everything runs successfully.

Is this a 64-bit issue?

This is very frustrating as I am trying to get management at my office to green-light the use of NCover and TestDriven.Net (including the purchase of 10 licenses) on a daily basis with our continuous build tools (CCNet in particular)

Montana

Re: 1.5.4. NCover fails with: Unable to establish communications

Are you saying that one of your machines is running the 64-bit version of Windows XP? And that one is having the NCover issues?

There is a known issue with NCover and 64-bit support which I am sure Peter will properly fix in a future release, In the meantime there is a workaround some people have reported success with you could try... see the updated FAQ temporarily located at:

http://www.kiwidude.com/dotnet/NCoverFAQ.html

Which has an entry linking to this thread:

http://ncover.org/SITE/forums/thread/43.aspx

Re: 1.5.4. NCover fails with: Unable to establish communications

Sorry, I wasn't clear in my specification.

I have an AMD Athlon X2 64-bit processor but I am running the Windows XP Professional 32-bit operating system.

At work I have a Pentium 4 with Hyperthreading (single core).

Is there a known problem running on a 64-bit processor or a dual-core cpu?

Kind Regards,

Montana

Re: 1.5.4. NCover fails with: Unable to establish communications

I figured out my own problem (knock on wood).

All I had to do was add the regsvr32.exe call for coverlib.dll in my batch file and I no longer see the disconnection message.

I appreciate the help anyway.

Montana

Re: Profiling IIS Applications

restart the iis....

then surf on your site, when the process is created, it monitors it.

but it doesnt produce me an xml file. the log is written.....

Re: Profiling IIS Applications

Is there any documentation anywhere on this? Please?

Its great functionality to have, but what's the point in creating it and distributing it if you don't also tell people how to use it?

Re: Profiling IIS Applications

There are 2 problems to overcome when profiling IIS apps.
1. NCover doesn't seem to know when to stop profiling an IIS app, so after testing, stop (or restart) IIS, and this will let NCover know that you're done.
2. Then there seems to be a bug in ncover.console which prevents the coverage data from being collected. The culprit is in Message.cs line 163 (version 1.5.4-b) which throws an error when profiling IIS. Change this line to:

else if ((proc != null) && (proc.HasExited))

and recompile and you should be good to go. The build will report an error about atlbase.h not found since if you don't have VS2005 and C++ installed. Luckily the build will still produce ncover.console.exe even if the error occurs. Other DLLs (coverlib.dll) will not be produced but if you have the binaries for 1.5.4-b, you can just use the DLLs there.

I am using NCover to profile a web application and I have my tests written with NUnitASP. I wish NCover would support starting a process via command-line AND profiling with IIS. This way I can start my tests in NCover and have my test code plus my web application code profiled. Right now, I have to run my tests in a different process and have NCover dedicated to profiling my web app.

Anyways, I'm just happy that I can get coverage on my web app. Hope this simple fix helps you all.

vince