slabko
25-Apr-2009, 02:14 AM
Hello,
After working more with EurekaLog I think that exposing types from ICSharpCode in EurekaLog.dll as public is, in fact, a bug:
- it conflicts with the original ICSharpCode dll and does not allow to include both dlls in a project, so the original dll must be removed from the project in order to use EurekaLog
- since EurekaLog does not expose all types from ICSharpCode, there is no way to use both EurekaLog and other compression modes besides ZIP in a project
- deactivating EurekaLog removes EurekaLog.dll reference from a project and thus removes all ICSharpCode types from the project, and I would have to manually put back ICSharpCode original dll otherwise the project will not compile
A way to solve this bug would be either to hide ICSharpCode types in EurekaLog.dll (make them internal) or completely remove them and ship the original ICSharpCode dll with EurekaLog.dll.
It would be really great if this is solved in the next build, and the next build would be available soon.
Thank you!
Dmitry
After working more with EurekaLog I think that exposing types from ICSharpCode in EurekaLog.dll as public is, in fact, a bug:
- it conflicts with the original ICSharpCode dll and does not allow to include both dlls in a project, so the original dll must be removed from the project in order to use EurekaLog
- since EurekaLog does not expose all types from ICSharpCode, there is no way to use both EurekaLog and other compression modes besides ZIP in a project
- deactivating EurekaLog removes EurekaLog.dll reference from a project and thus removes all ICSharpCode types from the project, and I would have to manually put back ICSharpCode original dll otherwise the project will not compile
A way to solve this bug would be either to hide ICSharpCode types in EurekaLog.dll (make them internal) or completely remove them and ship the original ICSharpCode dll with EurekaLog.dll.
It would be really great if this is solved in the next build, and the next build would be available soon.
Thank you!
Dmitry