I recently upgraded a project to .Net 8.
One UI issue that occurs now is that my UltraDateTimeEditors no longer close when a user manually selects a date.
Previously, if the tool was opened you would get the month view and if the user selected a different date (say 9/26) on the calendar the tool would close (using the month to month arrows did not).
Now, if the user selects a different date the tool just remains open.
Is there anyway to achieve the previous behavior? (I believe that UltraDateTimeEditor is built on datetimepicker, but I could not find anyone complaining of this issue, or know issues, for either component).
Hello Bradley,
Thank you for you post. May I know which version of infragistics control you are using ?
With .net 8 are you using dlls or packages because dll wont support core project, you would have to use nuget packages with .net 8 application.
If you are already using package and still having the issue then can you share your demo sample reproducing the issue for further investigation.
At my end I am not able to reproduce the issue. Attached my sample for your reference.
Regards,
3324.WinFormsApp1.zip
Hi Divya, Thank you for your reply. I am using 23.2.81 NuGet.
I took your project and downgraded the NuGet to this version and also upgraded your .Net6.0 to .Net 8 etc (using the CLI tool, as I did for my project previously from an earlier version).
I was not able to reproduce my issue here.
I examined the properties of one of my controls and the one in your sample project, I did not see any issues with properties they share.
The only oddity I have noted so far is that my control has an extra property - ContextMenuUltra on ultraToolbarsManager set to (none) .
Note: I have 4+ UltraDateTimeEditors with this issue (There is a DateTimePicker that does not have this issue).
I will continue to try to reproduce the issue, but I wanted to give you an update and thank you for your efforts thus far.
Hello,
Thank you for the update .Yes i believe that should not be turned off, but if you have any specific reason and if all other controls are working fine then we can continue investigate this behavior.
Hi Divya,
I was finally able to reproduce the issue in the test project.
It seems to be a side effect of having ApplicationVisualStyles set to false. This normally defaults to true in the ApplicationConfiguration.Initialize call unless overridden via the .csproj file or if chosen to not include this initialize call (and instead call the individual methods called by this generated method).
We had this turned off in our application. I am currently trying to discover internally if this was purposeful or an oversight.
Microsoft link for reference:
https://learn.microsoft.com/en-us/dotnet/desktop/winforms/whats-new/net60?view=netdesktop-6.0#new-application-bootstrap
Thank you for the update. let me know if you are able to reproduce the issue.