Question by MasterLG · Apr 12, 2017 at 05:09 AM · script error ide

How to "disable" obsolete Unity 4 (and prior) scripting warnings/errors in Unity 5?

Now that I'm using Unity 5, it would be good to disable all of the obsolete features for warnings I can't use.

For example, I can't use Rigidbody rigidbody as a variable on a MonoBehaviour without declaring it as new, but I can't use the inherited member anyway since it's obsolete.

Is it possible to turn off these warnings (turning them into straight-up compiler errors) and make it so that it's attempting to compile for what I'm actually using, without making me have to use keywords and whatnot to make a compiler happy about things that don't exist anymore?

Add comment · Show 5

hexagonius · Apr 12, 2017 at 06:23 AM 0

The way I do this, whenever I'm desperate to use one of the old names, I wrap the declaration with the following directives:

 #pragma warning enable 108
 Rigidbody rigidbody;
 #pragma warning restore 108

This tells the compiler to ignore CS 108 warnings for that single line. This technique can be used for whatever warning mono or unity is giving you.

I don't know if you can make these errors, but I wouldn't see how that's useful, because then you have to change them what you can do when it's just warnings as well

Show more comments

tanoshimi · Apr 12, 2017 at 06:50 AM 0

Interesting question, although I had to read it twice to understand. I think ins$$anonymous$$d of "disable all of the obsolete features for warnings I can't use" you meant to say "disable all of the warnings for obsolete features I can't use"?

I don't have an answer, other than to say that if things like the .rigidbody inherited member variable are marked as deprecated, they will be completely removed in a future version of Unity, at which point your warnings will presumeably disappear.

Show more comments

tanoshimi · Apr 12, 2017 at 07:03 AM 0

You can make all warnings act as errors by adding -warnaserror+ to the Assets/mcs.rsp file. Does that help?