Comments on: On Getting Rid Of Common Libraries… What About Don’t Repeat Yourself? http://davybrion.com/blog/2009/05/on-getting-rid-of-common-libraries-what-about-dont-repeat-yourself/ inquisitive: adjective. given to inquiry, research, or asking questions; eager for knowledge; intellectually curious Wed, 08 Feb 2012 11:42:42 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: neil martinhttp://davybrion.com/blog/2009/05/on-getting-rid-of-common-libraries-what-about-dont-repeat-yourself/comment-page-1/#comment-14414 neil martin Tue, 05 May 2009 18:26:59 +0000 http://davybrion.com/blog/?p=1372#comment-14414 I think it depends on what you are doing for research projects or slow moving projects i tend to have a static library against which i know my code will compile and work i tend to put this in the lib folder i also tend to create dll references to anything that this might need form other dll's i have built in this fashion i ensure that this code is statically versioned and just works.When i am dealing with production code i tend to use SVN: external style model and share a lib. When i deploy frameworks and the likes i tend to merge them into sensible grouped dll's such as.Objects .Tests .Tests.ObjectInside this are a number of folders so the code is split down further into sensible groups within the dll's.neil I think it depends on what you are doing for research projects or slow moving projects i tend to have a static library against which i know my code will compile and work i tend to put this in the lib folder i also tend to create dll references to anything that this might need form other dll’s i have built in this fashion i ensure that this code is statically versioned and just works.

When i am dealing with production code i tend to use SVN: external style model and share a lib. When i deploy frameworks and the likes i tend to merge them into sensible grouped dll’s such as

.Objects
.Tests
.Tests.Object

Inside this are a number of folders so the code is split down further into sensible groups within the dll’s.

neil

]]> By: Jackhttp://davybrion.com/blog/2009/05/on-getting-rid-of-common-libraries-what-about-dont-repeat-yourself/comment-page-1/#comment-14280 Jack Mon, 04 May 2009 08:26:25 +0000 http://davybrion.com/blog/?p=1372#comment-14280 While, I also use my common library. with my lib, I can write applications fast, so I like my library. After seeing your article, I think I do need to upgrade my library often but not give it up. While, I also use my common library. with my lib, I can write applications fast, so I like my library. After seeing your article, I think I do need to upgrade my library often but not give it up.

]]> By: efdeehttp://davybrion.com/blog/2009/05/on-getting-rid-of-common-libraries-what-about-dont-repeat-yourself/comment-page-1/#comment-14212 efdee Sun, 03 May 2009 16:47:57 +0000 http://davybrion.com/blog/?p=1372#comment-14212 I had the feeling that Ayende was mostly complaining about the fact that alot of what's in Rhino Commons isn't being reused, it's just in there because it was used in another project and, at that time, seemed to have potential for reuse.In contrast, it sounds like what you are describing are pieces of code that are actively being reused and maybe could be considered micro-frameworks in their own respect (which I don't think Ayende was referring to).Maybe you should refactor these micro-frameworks away from your "common" library and see what is left in the latter afterwards, and how reusable that is.Ofcourse, maybe I myself misunderstood both blog posts ;) I had the feeling that Ayende was mostly complaining about the fact that alot of what’s in Rhino Commons isn’t being reused, it’s just in there because it was used in another project and, at that time, seemed to have potential for reuse.

In contrast, it sounds like what you are describing are pieces of code that are actively being reused and maybe could be considered micro-frameworks in their own respect (which I don’t think Ayende was referring to).

Maybe you should refactor these micro-frameworks away from your “common” library and see what is left in the latter afterwards, and how reusable that is.

Ofcourse, maybe I myself misunderstood both blog posts ;)

]]> By: Davy Brionhttp://davybrion.com/blog/2009/05/on-getting-rid-of-common-libraries-what-about-dont-repeat-yourself/comment-page-1/#comment-14188 Davy Brion Sun, 03 May 2009 11:10:15 +0000 http://davybrion.com/blog/?p=1372#comment-14188 @KenWhat happens when 2 projects point to the same specific version, and someone from project A makes a change in the external common stuff that has an impact on project B? @Ken

What happens when 2 projects point to the same specific version, and someone from project A makes a change in the external common stuff that has an impact on project B?

]]> By: Ken Egozihttp://davybrion.com/blog/2009/05/on-getting-rid-of-common-libraries-what-about-dont-repeat-yourself/comment-page-1/#comment-14106 Ken Egozi Sat, 02 May 2009 20:00:31 +0000 http://davybrion.com/blog/?p=1372#comment-14106 something like svn:externals could serve as a good answer. a single repository in the company for the good-stuff. Every project gets full source control access (thus can fix things and step into if needed), and every project can point to a specific version to avoid dependency hell. something like svn:externals could serve as a good answer.
a single repository in the company for the good-stuff. Every project gets full source control access (thus can fix things and step into if needed), and every project can point to a specific version to avoid dependency hell.

]]> By: Morten Lyhrhttp://davybrion.com/blog/2009/05/on-getting-rid-of-common-libraries-what-about-dont-repeat-yourself/comment-page-1/#comment-14102 Morten Lyhr Sat, 02 May 2009 19:35:51 +0000 http://davybrion.com/blog/?p=1372#comment-14102 Compile it all into one assembly, with different namespaces, and use ILMerge to get ‘one assembly per physical deployment‘ rule again./Morten Lyhr Compile it all into one assembly, with different namespaces, and use ILMerge to get
‘one assembly per physical deployment‘ rule again.

/Morten Lyhr

]]>