-
Notifications
You must be signed in to change notification settings - Fork 18
do not allow c# builds with warnings #3867
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
do not allow c# builds with warnings #3867
Conversation
|
| <PropertyGroup> | ||
| <TreatWarningsAsErrors>true</TreatWarningsAsErrors> | ||
| <WarningsNotAsErrors>CS1998</WarningsNotAsErrors> <!-- optional --> | ||
| <NoWarn>CS0618</NoWarn> <!-- optional --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure if these exceptions are necessary
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, these are just syntax examples.
|
|
||
| return (!option.NwRegardIp || nwObject1.IP == nwObject2.IP && nwObject1.IpEnd == nwObject2.IpEnd) | ||
| && (!option.NwRegardName || nwObject1.Name == nwObject2.Name); | ||
| return (!option.NwRegardIp || (string.Equals(nwObject1.IP, nwObject2.IP, StringComparison.Ordinal) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
here using case sensitive, in appServerComparer case insensitive. Maybe we should think about centralizing /harmonizing this setting



fixes #3866