System.Data.SQLite

Login
This project makes use of Eagle, provided by Mistachkin Systems.
Eagle: Secure Software Automation
2011-10-04
09:20 Ticket [0d5b1ef362] SQLiteLog.DomainUnload registered many times status still Closed with 1 other change artifact: 7af3ed0f77 user: mistachkin
09:15
Only add the vendor-specific package path to the process environment once. Also, remove unnecessary test constraints from the test for ticket [0d5b1ef362]. check-in: f502c8b48f user: mistachkin tags: trunk
08:06 Closed ticket [0d5b1ef362]: SQLiteLog.DomainUnload registered many times plus 4 other changes artifact: b809c056ec user: mistachkin
08:05
Prevent the SQLiteLog.DomainUnload method from being added multiple times to the AppDomain.DomainUnload event, ticket [0d5b1ef362]. Stop trying to configure the SQLite logging interface in non-default AppDomains, ticket [ac47dd230a]. check-in: 3054af47e2 user: mistachkin tags: trunk
04:10 New ticket [0d5b1ef362] SQLiteLog.DomainUnload registered many times. artifact: f1142b6e72 user: anonymous

Ticket Hash: 0d5b1ef3627fba7ad6e60e521ea0cb0457db7ef8
Title: SQLiteLog.DomainUnload registered many times
Status: Closed Type: Code_Defect
Severity: Minor Priority: Immediate
Subsystem: Logging Resolution: Fixed
Last Modified: 2011-10-04 09:20:13
Version Found In: 1.0.75.0
Description:
SQLiteLog.Initialize registers its AppDomain unload event handler every time it is called, not just the first time when it initializes the logging callback.

This means that an extra copy of the unload event handler is added for every SQLiteConnection object that is created.

Only one is needed.


mistachkin added on 2011-10-04 08:06:24 UTC:
Fixed by check-in [3054af47e2].