SA1612 triggered by using reserved keywords as parameter names

[BennieCopeland]

The check SA1612: The parameter '{param name}' does not exist. is being triggered by parameters that use the prefixed keywords for parameters. I'm using the 1.1.0-beta001 version of the analyzer.

/// <summary>
/// SomeMethod summary
/// </summary>
/// <param name="event">Does something</param>
private void SomeMethod(string @event)
{
}

[bjornhellander]

OK. Thanks for the report!
For now, you can suppress the diagnostic and we will have a look at why this is happening.

[bjornhellander]

I'm fixing this. And I will try to see if there are similar problems with other rules.

[bjornhellander]

For the record, the problem was that the rule tried to get the parameter name through parameter.Identifier.Text, but that property contains the actual text written in the code, which in this case is "@event". On the other hand, parameter.Identifier.ValueText contains just "event", so I changed the code to use that property instead.