Related to some other issues we did an upgrade of our clients and our grid node server to version 3.19 yesterday evening.
Since that upgrade we receive the following error message while we try to run tests projects that have a reference on projects that have Code Analyses on Build enabled:
****************** BUILD OUTPUT FROM '<<Replaced Server Name>>' ******************
CA0001 : An unknown error occurred while running Code Analysis.
Disabling Code Analysis the tests will be executed fast and successful.
Would you please so kind to provide us steps to solve this problem?
Kind Regards
Sebastian
Build/Test Issues
Testing Projects with Code Analysis enabled fail on Grid Node Server with Version 3.19.
Started by GlobalConcepts on 4,144 views
Remco NCrunch Developer
#12639
06 Sep 2018 12:55 UTC
Hi, thanks for sharing this issue.
Another user has also reported this problem. v3.19 contained some refactoring around the code analysis suppression that shouldn't have resulted in a functional change, but apparently in some environments it has. I haven't yet been able to reproduce this problem.
I'm wondering if you could try adding a Custom build property of 'RunCodeAnalysis' = 'False' on each of the projects involved. Can you confirm if this suppresses the issue?
Another user has also reported this problem. v3.19 contained some refactoring around the code analysis suppression that shouldn't have resulted in a functional change, but apparently in some environments it has. I haven't yet been able to reproduce this problem.
I'm wondering if you could try adding a Custom build property of 'RunCodeAnalysis' = 'False' on each of the projects involved. Can you confirm if this suppresses the issue?
Thank you for your response!
Adding that Custom build property seems to work. Do we have to expect problems regarding "default" code analysis or is this just for ncrunch purposes?
Adding that Custom build property seems to work. Do we have to expect problems regarding "default" code analysis or is this just for ncrunch purposes?
Remco NCrunch Developer
#12644
06 Sep 2018 23:14 UTC
This custom property only gets applied when NCrunch builds your project, so there's no risk of side effects here. The property is the same one that NCrunch is actually supposed to inject into your build anyway (since CodeAnalysis is off), but somehow this is misbehaving. We'll get to the bottom of it. For the time being, this should be an effective workaround.
solved with 3.20 :-)
Thanks for that!
Thanks for that!
Post a reply
Log in to reply.