Exceptional does not understand the property exception xml doc that it generates about exceptionalresharper HOT 5 CLOSED

Both times I've encountered this issue has been when working with an indexer property. I do not know if this issue is exclusive to indexers.

from exceptionalresharper.

@wiredwiz do you have a sample of the code in use?

When the below kind of code is used seems to work fine:

/// <exception cref="SecurityException" accessor="set">Foo</exception>
public string this[string a]
{
    set
    {
        throw new SecurityException("Foo");
    }
}

from exceptionalresharper.

Ok, I'm not entirely sure what is going on now. I just checked the issue in the same instance of studio that has been sitting open since yesterday and now it seems to have corrected itself. Also, when I try to remove and recreate the comments now it behaves as it should. I guess there must have been some delay or confusion in the updating of the warnings or something. In any case I will close this issue till I can reliably reproduce this behavior again.

from exceptionalresharper.

Yes, I also noticed that there are some glitches with that...

from exceptionalresharper.

I will try to devote some time to reading over the source of this project so as to contribute back to it. I'm not familiar with creating ReSharper extensions at all but I'd like to help with some of this if I can find the free time.

from exceptionalresharper.