c# - Best way to organize third party libraries with console applications -


i build large number of console applications run business processes around here. of same nature, deployed application servers, access source database , place staged data target db. access file shares , like.

given setup, use same logging package (log4net) on , over. keep config in each app.config. but, keep finding have "carry along" dll log4net along me.

what mean when start new project, have make reference log4net. have chosen not put log4net in gac or install dev machine. instead have entire download package in directory , this:

i grab dll , create /lib directory in console app project , reference that.

the upsides seam know have right version because copy local dll. check in project.

but, downside end tons of projects each /lib directory, same dlls present.

what doing wrong? missing entire idea behind solution/project development? feel projects disparate don't want them load in 1 solution.

i curious hear how others tackle problem.

have looked @ ilmerge? should able ilmerge log4net.dll executable make standalone.

example usage (as post-build step):

"$(solutiondir)lib\ilmerge" /targetplatform:v4,c:\windows\microsoft.net\framework\v4.0.30319 /out:$(projectdir)bin\merged\myexe.exe myexe.exe log4net.net40.dll 

Comments

Popular posts from this blog

assembly - 8086 TASM: Illegal Indexing Mode -

Java, LWJGL, OpenGL 1.1, decoding BufferedImage to Bytebuffer and binding to OpenGL across classes -

javascript - addthis share facebook and google+ url -