Get Namespace from InvocationExpressionSyntax in Roslyn Analyzer

Question

I'm attempting to create an Analyzer for Roslyn that will prevent the use of Asserts within a given namespace (to ensure that the project design standard is maintained).

I've been able to get to the point where I can verify if this is an assert, but I am unsure how get the namespace from the context.

public override void Initialize(AnalysisContext context)
{
    context.RegisterSyntaxNodeAction(AnalyzeMethod, SyntaxKind.InvocationExpression);
}

private static void AnalyzeMethod(SyntaxNodeAnalysisContext context)
{
    var expression = (InvocationExpressionSyntax)context.Node;

    var memberAccessExpression = expression.Expression as MemberAccessExpressionSyntax;

    if (memberAccessExpression == null) return;

    var memberSymbol = ModelExtensions.GetSymbolInfo(context.SemanticModel, memberAccessExpression).Symbol as IMethodSymbol;

    if (!memberSymbol?.ToString().Contains("Assert") ?? true) return;

    //Check if we're inside the Page Namespace.


    //This is an Assert, lets fail it.
    var diagnostic = Diagnostic.Create(Rule, memberAccessExpression.GetLocation(), memberAccessExpression.Name);

    context.ReportDiagnostic(diagnostic);
}

When inspecting the context object itself, I can see a ContainingSymbol object, that contains a ContainingNamespace property, but when I try to code against this, I don't appear to be able to access it.

Whats the easiest method of getting the class namespace? i.e. I want the namespace of the class the Assert is in, not the namespace of the assert.

As a bonus question - Is there any decent documentation on any of this?

SLaks · Accepted Answer · 2016-09-22 18:34:46Z

2

ContainingSymbol returns the base ISymbol interface, which can represent any symbol.

To access more-specific properties, you need to cast it to a more-specific interface, such as IMethodSymbol.

answered Sep 22, 2016 at 18:34

SLaks

891k182 gold badges1.9k silver badges2k bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Obsidian Phoenix Over a year ago

So part of the issue is that I can't even see the containingsymbol property on the context. How do I get to it?

SLaks Over a year ago

That should work. source.roslyn.io/#Microsoft.CodeAnalysis/DiagnosticAnalyzer/…

Nyami · Accepted Answer · 2016-09-23 08:01:53Z

1

Make sure you have pulled down the latest packages via NuGet.

However I don't understand why you are able to see it at runtime using the debugger but unable to code against it.

answered Sep 23, 2016 at 8:01

Nyami

1868 bronze badges

3 Comments

Obsidian Phoenix Over a year ago

This was the winner. Seems strange that you can see it at runtime, but need the updated packages to be able to see it.

SLaks Over a year ago

@ObsidianPhoenix: If you're running in VS, you're using the latest packages at runtime regardless, due to VS bindingRedirects.

Obsidian Phoenix Over a year ago

@SLaks Thanks. So what happens if I code for the latest version and someone tries to use the package on an older VS2015 Update? Is it likely to break?

Collectives™ on Stack Overflow

Get Namespace from InvocationExpressionSyntax in Roslyn Analyzer

2 Answers 2

2 Comments

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related