In .net core v1.0 and v1.1, calling AseConnection.Dispose() multiple times still causes an ObjectDisposedException. Looks to be because of the Close() call done by base.Dispose, but only in v1.0 and v1.1
It looks to be safe to remove the _disposed check, as Close also confirms the state isn't Closed already before continuing.
Write some tests comparing AseException and AseErrorCollection behaviour differences between reference and our driver
Items to do before pushing out a nuget package:
In .net core
v1.0andv1.1, calling AseConnection.Dispose() multiple times still causes anObjectDisposedException. Looks to be because of theClose()call done bybase.Dispose, but only inv1.0andv1.1_disposedcheck, as Close also confirms the state isn't Closed already before continuing.Write some tests comparing
AseExceptionandAseErrorCollectionbehaviour differences between reference and our driver