Foxtrek_64
Custom Logger
I was able to figure it out.
My SqlServer library was named Microsoft.Extensions.Logging.SqlServer and the tests library adds the .Tests node to the namespace.
It was correctly pulling in appsettings data that told it that
So naturally an information message was being excluded.
I created a new type with a new namespace in my test library to simulate a consumer and now everything is happy
14 replies
Custom Logger
I do see a lot of calls to my logger provider's
CreateLogger()
function
_loggers
is a concurrent dictionary (made it that in case of this being issues with async, but it can probaby be a regular dictionary) of string, MSSqlDatabaseLogger.
The current options are provided by IOptionsMonitor<>
And the scope provider is an IExternalScopeProvider
instance, which defaults to a no-op scope shamelessly copied from the M.E.L.Console no-scope provider.14 replies
SqlConnection Connection Disposed
That's a good catch
Doesn't seem to pass a unit test though.
The test is pretty rudimentary - it checks the number of rows in a table, attempts to insert a row, checks the number of rows again, and asserts the counts are not equal (I'm sure there are better ways, it's just what worked in the few seconds that I was writing this test).
Before and after the insert both have the same number of rows.
13 replies
SqlConnection Connection Disposed
Nothing particularly special here, but I can share.
https://gist.github.com/Foxtrek64/ba9864e7c65bc9e8b42c7702d493a6dc
The interfaces are just for describing the features of the accessor. This library is intended to implement several types, like SqlServer and Mongo and a few others, but that's not particularly important. None of the interfaces here are DIMs.
13 replies