10

I was using Code Contracts in several projects and I was really satisfied with its static checker and propagated it across other developers. With new Visual Studio 2017 and .NET Core projects, I found two major drawbacks, which got me to look for an alternative. The first drawback is that Code Contracts aren't supported in Visual Studio 2017 and later versions, although there is a workaround for the static checker. The second drawback is that Code Contracts don't support .NET Core projects.

I would like to use static checking in my current projects (some of them are .NET Core based, others not) and I am looking for an alternative. One of the possible alternatives is Fody, but I don't have any experience with this IL assembly modifier.

Do you know about any better alternative tool for static checking?

1
  • 1
    Although there doesn't seem to be a concrete alternative at the moment, you would want to read this comment, and also vote and take part in this discussion. Mar 29, 2020 at 1:50

1 Answer 1

-1

Microsoft Visual Studio is extremely limited and .NET is even more limited. If you want to interact with both of these and bypass their premeditated limits, then I suggest using raw C++11 or later C++ versions and controlling Visual Studio and .NET from there. I currently use C++11 due to its extensive industrial applicability and CodeBlocks 17.12 due to its lack of back doors which I found in version 20+. I have never had any problem with static checking via simple and direct C++ code.

1
  • CodeBlocks is open source. Please post the names of the source files, the version numbers of those files, and the lines you claim contain these alleged back doors. Apr 5 at 6:25

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.