[Feature Request]: Add `[AllowNull]` to a controls `Text` field

[Smurf-IV]

Part of the improvements in .net 6 / 7:

from here: https://github.com/dotnet/winforms/commit/48616c47095149309b95caea9cc4e7c182313756

[PWagner1]

Making the project 'nullable' should help with this

[Smurf-IV]

As part of this merge https://github.com/Krypton-Suite/Standard-Toolkit/pull/933

The [AllowNull]able attribute is now backward compatible with previous frameworks.

This will fix most of the following warnings in the compile:

[PWagner1]

Reminder!!!!! This should ought to be part of the extended toolkit as well ;)

[PWagner1]

[PWagner1]

@Smurf-IV Disable CS0436?

[Smurf-IV]

The following should be preventing it from appearing in anything above core 3.1: #if NETFRAMEWORK || NETCOREAPP ????

[Smurf-IV]

@Smurf-IV Disable CS0436?

I'll check what Frameworks I have installed; to make sure it is just the supported list ;-)

[Smurf-IV]

Seems to be okay, I do not get the following

@Smurf-IV Disable CS0436?

[Smurf-IV]

@Wagnerp Why is there still netcoreapp3.1 in the Krypton support list ?

[Smurf-IV]

@Smurf-IV Disable CS0436?

This was caused by the following code

I'll fix it. (No idea why it was not showing up until I did a full rebuild !!

[PWagner1]

@Wagnerp Why is there still netcoreapp3.1 in the Krypton support list ?

@Smurf-IV I'll remove it in the next PR

[Smurf-IV]

Oh, wow.. This is turning into a big PR.. Following all the nullable entries around the code is also "catching / pointing out" some unexpected locations where things could/will have gone awry.

[Smurf-IV]

As of 2023-02-06:

Changed All Standard toolkit projects to be

• [x] <LangVersion>preview</LangVersion>
• [x] <Nullable>enable</Nullable>
• [x] <WarningLevel>6</WarningLevel>
• [x] <Optimize>True</Optimize> for release style builds (i.e. nightly, canary, as well as normal release)
• [x] Search for API's that return null and set there type to be nullable, e.g.
  • 
• [x] Trace back those API's and ensure nullable is applied to all derived API's
• [x] Check all API's that Force return null and set to nullable type, e.g.
  • 

ToDo:

• [ ] Search ALL API's that check for null and make there parameter(s) nullable
  • It just takes time:
• [ ] Search all code that is accepting the API return types and set there local var to be nullable
• [ ] Attempt to fix as many of these as possible:
• [ ] Other code fixes when it shows that a check for null should have been done now that the code is actually stating that the API could return null ! (Catch those edge conditions !!)
  • 
• [ ] Search for and correct using ??= or ?? conditions
• [ ] Search for things using FirstOrDefault to perform a return or var set.
• [ ] Check ?. usages

[Smurf-IV]

Note: The warnings and the enablement of these "Nullable" items will be ongoing, as other Features and Bugs are being worked on.

[Smurf-IV]

This may appear to be "dragging on" But even this past week MS are still pushing PR's into WinForms that are dealing with nullables ;-) https://learn.microsoft.com/en-us/dotnet/desktop/winforms/whats-new/net80?view=netdesktop-6.0#miscellaneous-improvements