Bug – Code Analysis doesn’t work well with async methods even in Visual Studio 2013

Updated: Please see the status of FxCop/Code Analysis in this post

Yeah. That’s bad.. We are extensively using async/await in most of our projects. We have a guideline for developers to follow the code analysis with our own custom ruleset. We even run CA on CI (Yes! Initially, we were using FxCop on CI but we found one blocking issue that makes us to stop using FxCop on CI). but now, we found that CA is not able to analyze the async methods in both Visual Studio 2012 and Visual Studio 2013 RC.

What to do?  I am still thinking whether I should start looking for other tools (“What static analysis tools are available for C#?“) or I should just wait for Microsoft to fix the issue…

Code Analysis Issue with async method

3 thoughts on “Bug – Code Analysis doesn’t work well with async methods even in Visual Studio 2013

  1. Hi Stuart,

    Thanks for dropping by.

    Yes. I aware of ‘async void’ issue but my intention of this article is just to show that Code Analysis is not working when we are using async/await. It’s like a known issue for old CA. but CA on VS2015 works.

Leave a Reply

Your email address will not be published. Required fields are marked *