Thanks - Let me know if you need anything further from us 
1 Like
Hi @mickaelcaro - Sorry to chase again. Just wondering if you’ve got any updates on this ? This is a critical aspect to our builds/deployments. Thanks
Hi @ArronH
Would it be possible for you to run the analysis with at least the current LTS (7.9) of SonarQube side by side (i don’t want you to upgrade -yet-) to see if the analysis goes well again ? Just for me to see if that issue is related to this old version of SQ only.
Thanks in advance.
Hi @mickaelcaro - It may take a while but I’ll start working on installing that version on another instance and try the build however I have seen this post C# Files are not being analyzed with Sonar Cloud and Azure DevOps pipeline which seems to be the same issue and he was using a later version of sonar (Enterprise v8.4.1) ?
I don’t think this is the same issue (even if the final “error” is the same), that’s the point
Ok , will try get it running on v7.9 and let you know the outcome
1 Like
@mickaelcaro - Were in the progress of getting a new instance setup with that version however it may take a while to setup as we have to speak with other teams internally to get firewall rules applied etc…
Is there anything else in the meantime we can do to try do to troubleshoot further on the current version?
@mickaelcaro - I’m still working on trying to get a build running on a later version - Facing a few other issues not related.
Is there anything else we can try in the meantime on the current version ?
Hi @ArronH
I’m sorry i’m not in full time searching for a solution here, i might be able to work on it end of this week.
I don’t see any obvious workaround of test to do here, i’ll let you know if i find one.
Sorry for the inconvenience !
Mickaël
Hi @mickaelcaro - I’ve ran a build on the SonarQube version you mentioned and it still scans C# so it looks like the latest version of the sonar tfs extension isn’t compatible with the current version of our SonarQube instance. We’ll look to upgrade this.
Thanks for the help.
Hi @ArronH
Glad it works with that version. However i need to know on my side what is causing this. I’m running out of time these day to look at that but i’ll do my best.
Would you be able to send me a reproducer maybe ? That would be super helpful.
Mickaël
Hi @mickaelcaro
It would be good to find out what the issue is and potentially fix/provide a workaround for this SonarQube version as we haven’t upgraded our instance for a while so we’re not fully prepared at the moment to do this on our production instance.
Regarding sending you a reproducer - Can I just check you’re referring to this C++ developers now benefit from more efficient analysis and deeper Core Guidelines coverage ? - If so I’m assuming I should run this on our current version where the code fails to scan C#. How would I enable this , would just adding ’ sonar.cfamily.reproducer=true’ to a the variable within the tfs build be sufficient?
@mickaelcaro - I’m trying now to add that variable. Looks like I should be adding a path to the variable value as suggested here https://jira.sonarsource.com/browse/CPP-850 rather than =true so I’m trying that now however if the step doesn’t fail (which it doesn’t) will this fail to output this file ?
That didn’t seem to output any file when specifying a location on the variable. I’ll await your reply to advise before doing any other actions - Thanks
Hi @ArronH
No it’s not that, i was just seeking for a sample project that reproduce this issue.
Mickaël
Hi @mickaelcaro - I wouldn’t be able to share our code with you I’m afraid (I think that’s the ask?). Do you have any projects internally that you can use ? I would have thought the issue would occur with any C# projects that use the version of SonarQube we are using (v6.7.4) and the latest tfs extension (v4.17.0).
Yep. No problem, thanks anyway !
Hi @ArronH
I’m currently trying to investigate this issue (finally ! ) Can you please give me the version of the C# analyzer you have currently installed on your SQ 6.7 instance please ?
Thanks !
Is that a possibility for you to update this analyzer to at least version 6.7 ?