#pragma warning disable & restore

问题:

I have used c# to create a First Project. I have many warning errors and all these warning errors are to be single Error(Internal compiler error. See the console log for more information.)

For Reducing the warning errors I used #pragma Warning disable . #pragma warning restore front and back of the problematic code.

I have doubt that in my final build I should leave that #pragma warning disable & restore as it is in the program; or do I need to remove that? e.g:

#pragma warning disable
if (Displayer.instance != null && CTR.Tore== "Keepit")
{
    Displayer.instance.SetFielderProfile (i);
}
#pragma warning restore

For final build do I need to remove that or not?

回答1:

At the very least you should be specific about which warnings you've deliberately chosen to ignore. That way, if later maintenance introduces a 'new' warning/issue that you should be made aware of, the warning about the newly-introduced error won't be suppressed by your blanket pragma warning disable directive.

You can get the warning numbers pertaining to the build issues you've decided to ignore from the build Output window in Visual Studio. They're usually labelled "Warning CS0168...." or similar. In which case you can specifically target just the those error(s) you've decided to ignore like so:

#pragma warning disable 168, 3021

    //Your code that generates warnings CS0168 and CS3021 here

#pragma warning restore 168, 3021

回答2:

If it is code of any practical value you should not have any warning and compile with "warnings as error" setting with all warnings turned on.

Code you showing does not seem like it have any errors in itself. So I see no reasons why you need the pragma.

But it is really your call - your code and if no one need to use/look/pay for it - do whatever works for you.

回答3:

I got this error in my asp.net mvc (.net core) application. Based on this above and other article show this error comes from your c sharp code in chtml side.

To identify the issue, just open console or open cshtml in separate window.

I have a popup where this error comes, I separately open this popup and while investing error in console, I got that one semi-colon not in cshtml, so while rendering chtml it throw the error.