OK, but I think we are not focusing on the real problem. Forget about opening the same storage at the same time, I won't do it if it is not supported. Altough I need to be able to open a storage file in read-only using the .NET component. In this scenario I do not want to storage to be altered in any way. But I don't know why, there is a problem closing the storage when I opened it in read-only. It raise a SolFS error exception and after it comes an Acess violation exception. SolFS Explorer seems to be able to open the storage in read-only and closing it without any error or problem. Me I try to do that and it crash my app.

Second problem, I upgraded my .NET to 3.1.0.73 and when I open an existing storage file, read operation on stream seems to lock undefinitely.

cfalardeau wrote:
OK, but I think we are not focusing on the real problem. Forget about opening the same storage at the same time, I won't do it if it is not supported. Altough I need to be able to open a storage file in read-only using the .NET component. In this scenario I do not want to storage to be altered in any way. But I don't know why, there is a problem closing the storage when I opened it in read-only.

If we open the storage in read-only mode, it's closed fine in our tests.

SolFS Explorer doesn't use .NET wrapper, and this seems to be a problem of the .NET class IF it exists.

OK after check my project settings, I finally acknowledge that I was binding to the SolFSNet.dll in the C:\Program Files\EldoS\SolFS\dotNET\Managed that is not the current version 3.1.0.73. Then I revised my project settings again and flush any remaining dll in the debug directory and rebound my project to the SolFSNET.dll in the GAC that is 3.1.0.73. You were right! It works correctly for opening read-only storage file. I made a mistake and I'm deeply sorry.

But I still have the dead lock problem and I've attached a example program to allow to reproduce it.

We use cookies to help provide you with the best possible online experience. By using this site, you agree that we may store and access cookies on your device. You can find out more about and set your own preferences here.