Wondering if you can shed any light onto the following issue I am having with WinDayView (or CalendarInfo)
I have an WinForms application running .NET 2.0 framework using Infragistics Win 8.3
I am trying to update this application .NET 4.0 framework using Infragistics Win 14.2
The upgrade was pretty smooth with only some minor behaviour differences that I needed to code around but I do have a problem trying to run these two version concurrently (different computers but same environment). We wanted to do some testing to see how the two would co-incide and whether there would be any migration issues etc.
Please note: We are using ADO.NET databinding to DataSet/Datatable objects. We are using the "ALLPROPERTIES" binary binding to store an "ExtendedAppointmentInfo" Class in the Appointment.Tag. The "ExtendedAppointmentInfo" class has NOT changed at all between these version. It is not an external DLL, it is built in to the standard assembly. So I guess from that perspective, the assembly version number (semver) and CLR runtime versions have changed.
This is the current state of play;
I suspect this is something to do with Serialization, because if I go to the database and clear the "ALLPROPERTIES" binary field the appointment then appears. the problem however is that much of the other appointment information is gone also. Not a suitable workaround.
Having Read the following article I do not see anything in my "ExtendedAppointmentInfo" object which contravenes the suggestions within - https://msdn.microsoft.com/en-us/library/ms229752(v=vs.100).aspx
I can only assume that something has changed in the base Appointment Object which DOES not deserialize correctly in the .NET 2.0 Framework or the Infragistics Win 8.3 control.
Thanks in Advance!
Thank you reach out to us. Would you please provide us with an isolated sample that reproduces this behavior? Trying to load appointments in your app between different CLR versions should work but it needs to be tested. I'd be more than happy to test this for you and determine if there is indeed an issue.
Let me know if you have any questions regarding this matter.
I really would like to provide an isolated sample, but I don't really have the time at this minute to build such samples up. My workaround at this stage is just to deploy ALL users with the updated version - don't allow mixed usage between the versions.
This only became a problem because we thought we would give a single user a preview/play of the new version before rolling it out everywhere.
Again - I am very sorry I can't provide the samples.
As you said - loading the appointments in my app between different CLR versions should have worked but would require testing - testing which I am not sure is particularly important given the fact I am migrating from such an old version (8.3) to 14.2
I haven't managed yet to reproduce the behavior. Let me know if you need me to investigate this further.