You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently I setup a new build server that uses VS 2017 for builds and executes the tests within VS.
Our old build server and all our dev machines all run the tests fine but this one new build server for some reason is throwing this exception during the build process on a few of our tests ...
NCalc.EvaluationException: Type 'System.Diagnostics.TraceEventCache' in assembly 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' is not marked as serializable.
Have you guys ever come across this?
Looking at the capabilities the only difference I could see was that the old build box used the previous version of VS (2015) and the new one uses 2017, both VS versions are Enterprise.
Other than that everything seems to be the same except for the OS as our old build box was a windows 10 box the new one is a server (windows 2016).
Maybe this is something to do with running the build process on a server?
The text was updated successfully, but these errors were encountered:
Recently I setup a new build server that uses VS 2017 for builds and executes the tests within VS.
Our old build server and all our dev machines all run the tests fine but this one new build server for some reason is throwing this exception during the build process on a few of our tests ...
NCalc.EvaluationException: Type 'System.Diagnostics.TraceEventCache' in assembly 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' is not marked as serializable.
Have you guys ever come across this?
Looking at the capabilities the only difference I could see was that the old build box used the previous version of VS (2015) and the new one uses 2017, both VS versions are Enterprise.
Other than that everything seems to be the same except for the OS as our old build box was a windows 10 box the new one is a server (windows 2016).
Maybe this is something to do with running the build process on a server?
The text was updated successfully, but these errors were encountered: