Menu
▾
▴
Re: [Nmock-general] Re: Strong naming nmock.dll
|
From: Jim A. <JA...@th...> - 2004-10-29 09:17:04
|
<FONT face=3D"Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size= =3D2><DIV>+1</DIV><DIV> </DIV><DIV>Jim</DIV><DIV><BR> </DIV><FONT= color=3D#990099>-----nmo...@li... wrote: ----= -<BR><BR></FONT><blockquote style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px;= MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">To: O= wen Rogers <or...@th...><BR>From: Mike Roberts <mike.= b.r...@gm...><BR>Sent by: nmo...@li....n= et<BR>Date: 10/28/2004 08:55PM<BR>cc: Levi Khatskevitch <lkhatske@though= tworks.com>, nmo...@li...<BR>Subject: Re: [Nmock-= general] Re: Strong naming nmock.dll<BR><BR><FONT face=3Dmonospace size=3D2= >+1 to strong-naming assemblies.<BR><BR>-1 to keeping unit tests in the sam= e assemblies as the code they are<BR>testing. But that's just my opinion...= <BR><BR>Mike<BR><BR>On Thu, 28 Oct 2004 21:34:21 +0630, Owen Rogers<BR><ORO= GE...@TH...>wrote:<BR>> <BR>> definitely +1. i = was going through and doing this for some of my other<BR>> projects this= weekend. it's long overdue for nmock. <BR>> cheers, <BR>> owen= . <BR>> <BR>> <BR>> ---<BR>> R. Owen Rogers<B= R>> ThoughtWorks Technologies (India) Pvt Ltd.<BR>> <BR>&= gt; ThoughtWorks - Deliver with passion!<BR>> <BR>>  = ;ThoughtWorks is always looking for talented people who are passionate abou= t<BR>> technology. To find out more about a career at ThoughtWorks= go to<BR>> <A href=3D"http://www.thoughtworks.com/career/" target=3Db= lank>http://www.thoughtworks.com/career/</A>. <BR>> <BR>>  = ;<BR>> <BR>> Levi Khatskevitch <BR>> <BR>> 28/10/20= 04 21:32 <BR>> T= o: nmo...@li... <BR>> = cc: Owen Rogers/Cana= da/ThoughtWorks@ThoughtWorks <BR>> Subject: = Strong naming nmock.dll <BR>> <BR>> = On my current project we keep most of our unit tests in the same assembly a= s<BR>> the code they're testing. There are two reasons for that: <BR>>= ; <BR>> 1) It keeps things simple with regards to references and t= he number of<BR>> assemblies involved <BR>> 2) It's easy to test inte= rnal types since we don't have to make them public<BR>> or use reflectio= n <BR>> <BR>> We keep tests in a sub-folder within each project= and exclude it from<BR>> release builds. <BR>> <BR>> It all= worked nicely until we needed to strong name one of our assemblies<BR>>= since strongly named assemblies obviously can't reference non-strongly nam= ed<BR>> nmock.dll. I see no harm in strongly naming nmock.dll, especiall= y since<BR>> NUnit.Framework.dll is already strongly named. So if I don'= t hear any<BR>> objections from you I'll just go ahead and add signing t= o the NAnt build<BR>> script. <BR>> <BR>> Please tell me if = you think it's a bad idea. <BR>> <BR>> Regards, <BR>> = - Levi <BR>> <BR><BR><BR>-- <BR>mike roberts | <A href=3D"http://m= ikeroberts.thoughtworks.net/" target=3Dblank >http://mikeroberts.thoughtwo= rks.net/</A>|<BR><A href=3D"http://www.thoughtworks.com/" target=3Dblank >= http://www.thoughtworks.com/</A><BR><BR><BR>-------------------------------= ------------------------<BR>This Newsletter Sponsored by: Macrovision <BR>F= or reliable Linux application installations, use the industry's leading<BR>= setup authoring tool, InstallShield X. Learn more and evaluate <BR>today. <= A href=3D"http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/" target= =3Dblank >http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/</A><BR>= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<BR>Nmock= -general mailing list<BR>Nmo...@li...<BR><A href=3D"= https://lists.sourceforge.net/lists/listinfo/nmock-general" target=3Dblank = >https://lists.sourceforge.net/lists/listinfo/nmock-general</A><BR></FONT><= /blockquote><br></FONT>= |
