We identified another issue: TeeChart has several dependencies. But, they are intended for internal use, I guess. Currently we are inheriting these dependencies which may result in unwanted, accidental use of these internals which may not be covered by the license. So, please hide these references. ...

I'm very happy that you get in detail with my questions! Anyway there is a question open. ... as we will need to continue to support Json v7 in the main TeeChart Nuget package You can support Json V7 also with referencing 6.0.X. I'm quite sure, all users can easily refer 7.0.X even you package defin...

Yes, we are using WPF. What are the 'organizational reasons' you refer to here? if you were able to give us cogent, compelling reasons for moving from v.7.0 to v.6.0 we could consider doing so. As stated initially, we have an internal package feed with approved packages. Currently net7 is not allowe...

In any case we have registered your concern and will bring it up for discussion in our next technical meeting. Great, when the next meeting is scheduled? For us, this will determine how we act in the short term. Maybe it is time for SixLabors to leave the beta phase. If it is used productive, it sh...

We want to update to recent version of Steema.TeeChart.NET, which is currently 4.2023.6.6. We found that some packages are referenced indirectly which does not fully apply to the quality rules of our company: 1. SixLabors.ImageSharp.Drawing and SixLabors.Fonts are referenced (directly and indirectly...