I reported an issue in JIRA earlier today in which I noted that ReSharper
isn't suggesting fixes for naming conventions in a nested structure. From
what I can tell so far, it looks as if this may apply to all structs
regardless of nesting.
I also noticed a couple instances in which ReSharper suggested making a
field read-only, but then it didn't prompt to fix the naming convention of
the field (this is in a standard class). In this case it's a protected
internal field and I see the squiggly line, but the quick fix popup has the
items to change or view the settings for the naming rule but not to fix the
naming convention. I pressed Alt+Enter on the item three or four times with
no change, so I fixed a couple other variables then came back to this one.
This time the quick fix worked. I've seen this behavior a couple times today
while refactoring a fairly substantial project, so it's not happening often
by any means.