Alexis Nowikowski

The current release supports EF Core v1.1.1, and probably also v1.1.2. It would be nice to support EF Core v2.0, I will surely take a look into this as soon...

Hi, It could be possible that the change tracking logic is triggering the LazyLoading. Please provide a piece of code which triggers this behavior.

@voodookoop Yes, you are right. The query cache contains entries, and these entries are also responsible for materializing the entity after querying the database (at least that's what I have...

Any workarounds? Still experiencing this issue...

I am also experiencing the `NullReferenceException` in v0.9.7, .NET 4.7: Stacktrace: ```at LiveCharts.ChartValues`1.d__12.MoveNext() in c:\Users\btord\Documents\Projects\LiveCharts\Core40\ChartValues.cs:line 219``` Code: ```c# _someLineSeries = new LineSeries { Title = "Some title", Values = someValues,...

@mariuszgromada I didn't change any default settings ```c# mXparser.checkIfAlmostIntRounding(); // true mXparser.checkIfUlpRounding(); // false mXparser.checkIfCanonicalRounding(); // true ``` I encountered this bug when I upgraded from 4.4.2 to 5.2.1. On...

@mariuszgromada On both 4.4.2 and 5.2.1 only AlmostIntRounding and CanonicalRounding are enabled by default. ```C# Version 4.4.2 mXparser.checkIfAlmostIntRounding(); // true mXparser.checkIfUlpRounding(); // false mXparser.checkIfCanonicalRounding(); // true Version 5.2.1 mXparser.checkIfAlmostIntRounding(); //...

> Can you run this code for me? > > ```c# > mXparser.disableAlmostIntRounding(); > mXparser.disableCanonicalRounding(); > mXparser.disableUlpRounding(); > String expStr = "0.0000004566969933 / 36370.51937825058"; > Expression testExp = new Expression(expStr);...

I am executing the code you sent me in the mXparser source UnitTests projects. I can see that it fails only for .NET Framework and .NET Standard libraries, for .NET...