|
|
|
|||||
|
bzip2.dll
Hi,
I am developing with Ice for .Net using c# with Visual Studio 2005. Everything works well, except for the fact that each time the Ice.dll is loaded I can see an exception thrown (note that this exception is internally caught, so there is no particular problem for running my program). This exception say that: 'myprog' (Managed): Loaded 'C:\myprog\bin\x86\Debug\Ice.dll', Symbols loaded. A first chance exception of type 'System.DllNotFoundException' occurred in Ice.dll Additional information: Unable to load DLL 'bzip2.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E) So it is about bzip2.dll. This dll is not a c# assembly but a c++ one it seems, so I cannot simply add it as a reference in my project. My question is: how can I ensure that bzip2.dll is found (and thus that compression features are enabled)? Thanks a lot in advance.
__________________
Sylvain Fasel Group of Applied Physics University of Geneva www.gapoptic.unige.ch Research in applied quantum cryptography |
|
|||||
|
Hi Dwayne,
Thanks for your reply. What you proposed is not very convenient when deploying an application, I think you'll agree. Ice.dll seems to search first for bzip2.dll being in the same folder, so I am looking for a way to instruct VS2005 to copy this dll into the build folder. It would be nice if bzip2.dll could be embedded in Ice.dll, so that we could deal with a single assembly. Regards.
__________________
Sylvain Fasel Group of Applied Physics University of Geneva www.gapoptic.unige.ch Research in applied quantum cryptography |
|
|||||
|
Well, adding bzip2.dll to the right project and setting its properties to "copy if newer" does the trick, but I would prefer a cleaner solution.
Thanks
__________________
Sylvain Fasel Group of Applied Physics University of Geneva www.gapoptic.unige.ch Research in applied quantum cryptography |
|
||||||
|
This really has little to do with Ice, and more to do with how Windows locates DLLs. Basically, for protocol compression to work, the Ice run time requires bzip2.dll. But that DLL may not be present on all machines. So, the run time tries to load the DLL dynamically and, if that fails, simply disables protocol compression.
Unless you actually need protocol compression, no harm is done. If you do need it, simply put bzip2.dll into the system or windows directory, where it will be found. See Dynamic-Link Library Search Order (Windows) for more information. Cheers, Michi. |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| DLL lost | queniao | Help Center | 4 | 12-03-2007 11:27 PM |
| use ice in dll? | cool stone | Help Center | 4 | 05-23-2007 06:52 AM |
| Traditional DLL being loaded by .NET DLL - Unable to Find dependencies | mboozell | Help Center | 3 | 05-02-2007 09:51 AM |
| Any benchmarks on using bzip2 compression? | wobster | Comments | 4 | 09-19-2004 09:13 AM |
| Missing DLL | dwforslund | Help Center | 7 | 02-19-2003 10:10 AM |