Why does VS2015 give me code analysis errors when VS2013 was completely happy?

I just opened an existing project in VS2015, and although it is completely built in VS2013, now I get errors like CS3002. The return type is not compatible with CLS in VS2015.

I checked the properties of the project, and “Enable code analysis on assembly” was not checked, and looked at the changes in VS2015, but I can’t see for life why these errors occur. Has something changed in Visual Studio?

+5
source share
1 answer

I just found an easy way around the problem. I used suppress to disable code analysis in my classes over the namespace.

#pragma warning disable 

This will not be a permanent solution. Maybe it will be useful for someone at the moment.

0
source

All Articles