You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
System.MissingMethodException
HResult=0x80131513
Message=Method not found: 'Void System.Threading.Mutex..ctor(Boolean, System.String, Boolean ByRef, System.Security.AccessControl.MutexSecurity)'.
Source=LiteDB
StackTrace:
at LiteDB.SharedEngine..ctor(EngineSettings settings)
at LiteDB.ConnectionString.CreateEngine()
at LiteDB.LiteDatabase..ctor(ConnectionString connectionString, BsonMapper mapper)
It works fine if I omit the connection specification. I managed to find a few odds and ends for this through google, but couldn't match to my particular use case. However, it looks like something to do with .net versions and Mutex (which I'm not familiar with)??
I did find this in your docs:
"The Shared mode only works in .NET implementations that provide named mutexes. Its multi-process capabilities will only work in platforms that implement named mutexes as system-wide mutexes."
However, I have no idea what this means, whether this applies to Framework 4.8 or not and indeed what to do as a result.
Version
I am developing on .net Framework 4.8 with LiteDb 5.0.17.0.
Describe the bug
When I try to instantiate a database connection with:
I get the following error:
It works fine if I omit the connection specification. I managed to find a few odds and ends for this through google, but couldn't match to my particular use case. However, it looks like something to do with .net versions and Mutex (which I'm not familiar with)??
I did find this in your docs:
"The Shared mode only works in .NET implementations that provide named mutexes. Its multi-process capabilities will only work in platforms that implement named mutexes as system-wide mutexes."
However, I have no idea what this means, whether this applies to Framework 4.8 or not and indeed what to do as a result.
Any suggestions?
Code to Reproduce
Expected behavior
Shared Connection is opened
The text was updated successfully, but these errors were encountered: