1.5.3 exclusion bug

From what I can gather with my testing, the exclusion feature works, with the following caveats:

1. Attributes are specified using their short, unqualified names, i.e. Test and TestFixture, not TestAttribute and TestFixtureAttribute, nor NUnit.Framework.TestAttribute and NUnit.Framework.TestFixtureAttribute

2. It only notices attributes if there is more than one attribute on the method/class. For example:

[Test]
public void One() {...}

[Test][Category("Foo")]
public void Two() {...}

[Test][ExpectedException(typeof(Exception))]
public void Three() {...}

Of the above three methods, the first would not be excluded, because it has only one attribute on it.

Re: NCover crashes when using with IIS

Did you try again with NCover 1.5.7?

Re: No coverage files produced if nCover is started remotely.

What user account is your automated tool starting NCover under? I'd look there first. The user account will probably be different from your login account and may not permissions to the registry or the file system as needed for coverage.

Re: No coverage files produced if nCover is started remotely.

I forgot to mention, my automated tool is actually logging in using a user account which is part of the "Administrators" group. I had made sure that both NCover and the service executable were also running under that user account (using the "User" column of task manager) . I am not sure about the registry but I would guess that any user with Administrative previleges automatically gets to use the registry. So, NCover running on that user account should be able to use the registry if it needs it to write the coverage files.

As you said, I suspected permissions problems and specifically enabled permissions for all the users on the system to read/write/... DO ANYTHING to the C:\Program Files\NCover folder.

Just to be sure, I also re-registerd the coverlib dll. Do the environment variables have to be set to (COR_PROFILER and something else I think ) ?

All the systems used are Windows XP SP2.