I think the fullcalendar is broken in 3.22

Hi Chris,

I can get and set UserData of an Event without any issues. See quick & dirty sample attached.

Best regards
Frank

Sorry, I the null-coalescing operator ?? does the conditional part as I understand (relatively new to c#), but fairly sure it still needs a set?

Done a test and the fullcalendar is working with preview , thanks for quick fix, one question though, it would appear from the description as a general storage object that the events UserData should have a set and not unconditionally recreate on each get?

Could be my c# understanding, there may be a way to work with it.

//     Returns a dynamic object that can be used to store custom data.
public dynamic UserData
{
get
{
dynamic obj = _userData ?? new DynamicObject();
object result = obj;
_userData = obj;
return result;
}
}

I will do some more tests on the JScharts issue and do a new post if cannot get anywhere.

Thanks

Chris

Hi Chris,

the issue with events not showing in the Full Calendar on .NET 7 is fixed and currently in QA.
If you want to test it before the release you can try Wisej.NET 3.2.3-preview7 on nuget.

I´m not sure I fully understand your issue with JSCharts. Any chance to wrap it up in a test case with more detailed instructions?

Thanks in advance,
Frank

Also, before I dig too deep, I think there may be a problem with the JSCharts extension with net 7 , as a preliminary test I set up as per the demo source, with a couple of tests, the core plot area of the chart does not seem to update, I am testing the bar with the demo code, its got 3 data sets loaded.

Looking at various ways to represent scheduling data with the extensions to showcase in company and get buy in, but have  unavoidable .net 6/7 dependencies in project and using all your latest stuff on dependency injection (which is working nicely).

Ah thanks, i need to target 7 in my deployment so much appreciated and glad it is not just me.

Hi Chris,

thanks for reporting this. I can see it fail with .NET 7 but working ok with .NET 4.8.
We´ll check and get back to you.

Best regards
Frank