The Log4Net mailing list is a great source of information about using log4Net, in this forum we collect all the messages in the log4net user list and some selected threads from the developer list.
| Author |
Messages |
|
boombox boy
 |
| 11/26/2008 12:22 PM |
|
Hi I have a custom log wrapper that utilizes log4net. I build a release assembly of MyLogWrapper.dll with log4net.dll reference set to copy-local true. Referencing MyLogWrapper.dll from MyProject with copy local set to true should result in log4net.dll being copied as well, right? I am not using any Log4net classes in MyProject as they are all wrapped in MyLogWrapper and therefore I do not reference Log4Net from MyProject. Dispite Log4net being a dependency of MyLogWrapper it is not being copied to MyProject output directory but all other dependencies of MyLogWrapper are. What could be the problem?
TIA
|
|
|
|
|
Radovan Raszka
|
| 11/26/2008 2:18 PM |
|
Hello.
In my opinion if you reference only MylogWrapper.dll from your project, only this DLL will be copied to the output directory.
If you need to copy log4net.dll automatically to the output, you must reference MylogWrapper project from your project or create post-build event which copies log4net.dll to output directory
Radovan |
|
|
|
|
boombox boy
|
| 11/27/2008 10:44 AM |
|
The thing is MyLogWrapper is built as a release library as it is used throughout all my different projects and therefore I do not want to have a project reference.
I tried removing log4net.dll from the GAC and now it seems to get copied locally as expected. Maybe someone could clarify on why this is the case?
BB
|
|
|
|
|
|
| You are not authorized to post a reply. |
|
|
|
ActiveForums 3.7
|