You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That checklist is a great idea! Here are a few points I usually set in my own libraries/apps, some with retro-compatibility requirements, I mostly wonder if it could be useful outside of my context, so it's more an open discussion than an issue :)
That checklist is a great idea! Here are a few points I usually set in my own libraries/apps, some with retro-compatibility requirements, I mostly wonder if it could be useful outside of my context, so it's more an open discussion than an issue :)
Rationale: you want to fix or document any warning.
Rationale: To avoid any conflict, and with latest version, you get extra help to modernize code.
Rationale: best explained here: https://devblogs.microsoft.com/nuget/enable-repeatable-package-restores-using-a-lock-file/
Rationale: to avoid an output rename that would conflict with existing code (more appropriate for exe than lib ?)
Rationale: needed for multitarget to .net framework when using resx.
Rationale: default is false: https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/compiler-options/language#checkforoverflowunderflow but still better safe than sorry, and add explicit bypass in code if needed
Rationale: boring but useful for libraries.
-Treat Warning as Error in Release
Rationale: effective way to keep the count low.
The text was updated successfully, but these errors were encountered: