0.10.0-beta3 keeping libsodium-64.dll locked

[grumpydev]

I'm using the latest beta and using these two methods in an ASP.Net app, currently hosting in IIS Express:

PasswordHash.ArgonGenerateSalt PasswordHash.ArgonHashBinary

The code itself is working fine, but once I've called those methods once the libsodium-64.dll seems to remain locked forever, so any attempt at rebuilding the solution fails because it can't copy the file - in order to do a build I have to kill IISExpress each time.

Is this expected behaviour or an issue with the beta? I'm only using statics so I'm assuming its not because I'm leaving something un-disposed?

[guysherman]

I am seeing this in the nuget version as well, when running unit tests. There's a workaround in the unit testing scenario because you can tell Visual Studio to get rid of the execution process each time. I suspect it is to do with the all the static LazyInvoke objects in SodiumLibrary, they must be keeping a handle to the dll open. SciTech's .NET Memory Profiler (memprofiler.com) is a great tool for getting to the bottom of this sort of thing.

[mdsharpe]

+1 happening here with xunit unit tests. Test execution engine keeps lock on libsodium.dll. Subsequent project rebuilds then fail because they cannot overwrite this file. This is with v0.10.0 final, not beta3.