Comments on: Re-Use is hard http://dynamicorange.com/2007/10/16/re-use-is-hard/?utm_source=rss&utm_medium=rss&utm_campaign=re-use-is-hard A low-frequency blog by Rob Styles Sun, 29 Apr 2012 07:29:20 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Rob Styles http://dynamicorange.com/2007/10/16/re-use-is-hard/#comment-894 Rob Styles Sun, 04 Nov 2007 08:48:57 +0000 http://dynamicorange.com/wpblog/2007/10/16/re-use-is-hard/#comment-894 Lyndsay, Interesting that you rebuilt to the lowest version. .Net, unlike pretty much any other environment, has the ability to load different versions of strong-named assemblies side-by-side at runtime. They have to be registered in the GAC (Global Assembly Cache) for that to happen, but it works extremely well. 'Notification' may make a better class than EmailNotifier... rob Lyndsay,

Interesting that you rebuilt to the lowest version. .Net, unlike pretty much any other environment, has the ability to load different versions of strong-named assemblies side-by-side at runtime. They have to be registered in the GAC (Global Assembly Cache) for that to happen, but it works extremely well.

‘Notification’ may make a better class than EmailNotifier…

rob

]]> By: Lyndsay http://dynamicorange.com/2007/10/16/re-use-is-hard/#comment-893 Lyndsay Wed, 17 Oct 2007 19:52:23 +0000 http://dynamicorange.com/wpblog/2007/10/16/re-use-is-hard/#comment-893 Nice article. We've hit this issue also, but slightly less hard as reuse is happening amongst the same team, writing side-by-side applications. The approach we've taken is to make an assembly "reusable" only when a second application requires the same functionality. So far the only challenge we hit here was dependancies - two apps were using different log4net versions, with differing strong names, so both apps and the component had to be rebuilt to take the lowest denominator. Components that are small and focussed have worked well so far, e.g. EmailNotifier, FileConverter (strange how they're more verb like than nouns eh - probably still too procedural :-) Nice article. We’ve hit this issue also, but slightly less hard as reuse is happening amongst the same team, writing side-by-side applications. The approach we’ve taken is to make an assembly “reusable” only when a second application requires the same functionality. So far the only challenge we hit here was dependancies – two apps were using different log4net versions, with differing strong names, so both apps and the component had to be rebuilt to take the lowest denominator. Components that are small and focussed have worked well so far, e.g. EmailNotifier, FileConverter (strange how they’re more verb like than nouns eh – probably still too procedural :-)

]]>