"Operation could destabilize the runtime." Since upgrade from 9.1.2 to 9.1.3

Since updatinng to 9.1.3 last Tuesday, we've been getting "System.Security.VerificationException: System.Security.VerificationException: Operation could destabilize the runtime.." exceptions on several unittest projects and builds.

My question is, what has changed in 9.1.3 w.r.t. 9.1.2 that could cause this. Is there some setting?
I've read online of several situations, but they don't seem to be applicable because before the TeamCity upgrade this was all fine

1. Unittests: This solved my problem http://stackoverflow.com/questions/3917374/why-do-my-tests-fail-with-system-security-verificationexception. I disabled the .Net Coverage tool. Question: Why does this occur now?

2. Builds: Not fixed yet. These builds use SWIG 3.0.4, could there be something with the DLL? The builds in old branches that use SWIG 3.0.2 are fine.
- http://stackoverflow.com/questions/7104424/using-structure-map-with-mstest
- http://stackoverflow.com/questions/378895/operation-could-destabilize-the-runtime

4 comments
Comment actions Permalink

Ok, the builds were completely my own fault... Was supposed to be using SWIG 3.0.7, the build agents didn't have this new dependency yet :)
Still, the .Net Coverage tool  seems to have an issue.

0
Comment actions Permalink

Hi Diana,

All the changes that could affect you while upgrade are listed in the Upgrade Notes. There were no related breaking changes between 9.1.2 and 9.1.3.
If the issue is still actual and build fails in TeamCity, then please use the guideline to investigate the issue.

0
Comment actions Permalink

We bumped into the exact same problem when we upgraded to 9.1.3 and disabling the code coverage fixed the problem.

I agree with Diana that code coverage tool must have introduced an issue on v9.1.3

0
Comment actions Permalink

Hi guys,

There is a known issue in dotCover: https://youtrack.jetbrains.com/issue/DCVR-7708. DotCover 10.0 is bundled with TeamCity 9.1.4 which is going to be released today.
Sorry for the inconvenience.

0

Please sign in to leave a comment.