EldoS | Feel safer!

Software components for data protection, secure storage and transfer

.NET CLR issues

Also by EldoS: CallbackRegistry
A component to monitor and control Windows registry access and create virtual registry keys.
#6078
Posted: 05/02/2008 10:16:02
by Nate Trost (Basic support level)
Joined: 05/02/2008
Posts: 2

Hi,
First off great products! We purchased your SolFS and love it. Now onto the question. With .net it is recommended to not create Shell/Namespace extensions due to the CLR being injected into explorer, so if the shell ext is created in CLR 2.0 and a CLR 1.1 program opens a file open/save dialog, it will crash the 1.1 program, because the 2.0 CLR is in-process of explorer. So do you know if the Callback File System is causing the .net CLR to be injected in-process of explorer?

Thanks,
Nate

P.S. here is the link to the explanation of CLR conflicts
http://blogs.msdn.com/oldnewthing/archive/2006/12/18/1317290.aspx
#6079
Posted: 05/02/2008 10:27:35
by Eugene Mayevski (EldoS Corp.)

Yes, we are aware of this problem. It's not specific to Explorer extensions: it can happen with any application with pluggable architecture. When one DLL is created with .NET 1.1 and another one is created with .NET 2.0, they will cause a conflict inside of the host process (Explorer or other application that uses these .NET-based DLLs).

Callback File System is a driver-based product. It doesn't contain DLLs written in .NET. So it doesn't cause such problems.


Sincerely yours
Eugene Mayevski
#6080
Posted: 05/02/2008 10:36:07
by Nate Trost (Basic support level)
Joined: 05/02/2008
Posts: 2

Hi,
Thats great thanks a lot for the quick response! Most likely will be purchasing Callback File System soon.

Thanks again,
Nate

Reply

Statistics

Topic viewed 4213 times

Number of guests: 1, registered members: 0, in total hidden: 0




|

Back to top

As of July 15, 2016 EldoS Corporation will operate as a division of /n software inc. For more information, please read the announcement.

Got it!