Where Do I Log Code Rules Bugs?


  • Code rules in Visual Studio would be a great feature, but they're buggy as all get out.

    Is there are GitHub repo where I can log issues?

    The main issues are that when you turn on code analysis, it sometimes does nothing. And yet, other times, once you've turned on code analysis, you can't turn it off again.

    I've logged the problem on Microsoft Connect before, but it just got ignored.

    Saturday, August 13, 2016 4:20 AM


All replies

  • Hi,

    Microsoft connect is the correct location for all bug reports.

    Could you link your bug report here?

    Or could you give a better example so that we can reproduce this issue?

    We are using code analysis for quite long and we never saw such an issue. (Which does not mean, that there is no bug, but I am curious if I could get this bug, too.)

    If others can reproduce this issue, they can vote up such an error report.

    With kind regards,

    Konrad Neitzel

    Saturday, August 13, 2016 4:56 AM
  • No. Microsoft Connect is not the correct location. I have logged several bugs there, and the only response I ever get is things like "Please provide a screenshot", or "Please provide a sample app". On the other hand, when I have been able to track down the correct GitHub repository, I am able to get rapid responses from the actual team that is working on the product.

    Anyway, I think you have answered my question in an indirect way. I logged this one a while back:

    If you don't believe this is still a bug in the latest version of Visual Studio, just try it out for yourself in a few different project types. It's a glaring hole in code rules, but as yet nobody has even acknowledged it.

    They responded with a potential workaround rather than acknowledging the bug. The workaround would be almost as cumbersome as manually correcting the automatically generated code.

    But the answer to my question is really this I think:

    I have logged one issue here:

    Saturday, August 13, 2016 11:03 PM
  • Hi  Melbourne,

    I have read the connect report in the link you shared. Yes, I agree with you. If this is a issue, they need to fix it instead of giving a workaround.

    #We are tracking this workitem on github here - I'll close this issue and provide further updates on the github issue.

    According to Srivatsn's description. They will track this issue in the GitHub  there. You could add your comments in that issue and wait for their response..

    Best Regards,

    Lake Xiao

    Monday, August 15, 2016 2:39 AM
  • I logged this bug here:

    I'm waiting to see if I get any response.

    Monday, August 15, 2016 3:09 AM
  • Hi  Melbourne,

    Please also add a comment to the Microsoft Connect. Tell them the new link of this issue in GitHub. I think Microsoft developer will track this issue in the new link as well.

    Best Regards,

    Lake Xiao

    Monday, August 15, 2016 6:30 AM
  • OK. I did that?

    Do you have any special powers to check to see if someone is actually looking at this?

    Monday, August 15, 2016 7:02 AM
  • Hi Melbourne,

    >>Do you have any special powers to check to see if someone is actually looking at this?

    Unfortunately, I haven't. You will receive the email once they look into this issue.

    Best Regards,

    Lake Xiao

    Monday, August 15, 2016 7:12 AM