1.5.4 exclusion bug

if we have class with exclusion attribute that we don't test then ncover will not exclude it.

Re: Problem when using Ncover with ASP.NET app.

Hi,

Chalk up another one.

I'm new to NCover, I just downloaded 1.5.8Beta I'm using the same setup as above except it's an ASP.NET 2.0 app. I get the same behavoir, seems to work well until the ASP page starts to load and then crashes with the same message. Thanks.

Re: Problem when using Ncover with ASP.NET app.

I've got the exact same problem, please guide us to get it working!

Re: Problem when using Ncover with ASP.NET app.

I'll try testing it on XP and see what I find. Are all of you running XP?

Re: Problem when using Ncover with ASP.NET app.

Yes, getting the problem on XP.

Re: Problem when using Ncover with ASP.NET app.

Yes, XP as well.

Re: Problem when using Ncover with ASP.NET app.

I have the same problem with Windows 2003 Web Edition....

Re: Problem when using Ncover with ASP.NET app.

Peter,

Do you have any status on this issue? Have you been able to reproduce the problem? Is there any additional info that we can provide that might be helpful? Thanks.

Re: Problem when using Ncover with ASP.NET app.

Same here with me a few more details on this post may help.
http://ncover.org/SITE/forums/thread/1250.aspx

XP as well

Re: Problem when using Ncover with ASP.NET app.

Same... on Server 2003 Enterprise and Vista Business x64 (corflags set to 32bit on NCover)

Re: Problem when using Ncover with ASP.NET app.

I have been trying to workout NCover for websites but i m unable to achieve the desired result.....

it says the Profiler API will not connect until u load the ASP.NET page....

Kindly guide me through this.

Thanks and Regards,

Shashank Sinha

Re: Problem when using Ncover with ASP.NET app.

Shashank,

Unless you are using a very old version of NCover or Windows Vista, the IIS support seems to be broken at the moment. In theory (mind you I've never actually seen this work yet, due to the aforementioned problem), once you attach NCover to the IIS process (with the //iis switch) all you have to do is point a browser to your page and start exercising it. However, since your interested in coverage, you probably really want to exercise the ASP.NET App in a more controlled fashion, via a test fixture (such as NUnit or VSTS). In that case, all you do is attach NCover to IIS and then launch you tests, once they complete you kill NCover (via Ctrl-C) and then examine the coverage results. Hope that helps.

Re: Problem when using Ncover with ASP.NET app.

Is there any update on this issue? Does anyone know exactly what previous versions DO work with //IIS?

Re: //h Option

Dmitry,

It's an uncompleted feature - I think Peter may have done some more work on it in 1.5.5 but am sure he will confirm if that's the case. Strictly speaking I don't think he should have even exposed the option as yet - as you found out it is completely useless in it's current state. The way the code is written in 1.5.4 it was also the case of generating xml OR html - which meant you had to do two coverage runs. I believe this is sorted in 1.5.5 as well.