Re: Is.Serializable
"Charlie Poole" <[email protected]> Mon, 8 Sep 2008 13:20:11 -0700
| Newsgroups | gmane.comp.windows.dotnet.nunit.user |
|---|---|
| Message-ID | <011101c911f0$4fb82060$6401a8c0@ferrari> |
This is a multi-part message in MIME format. --===============1669745205== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0112_01C911B5.A3594860" This is a multi-part message in MIME format. ------=_NextPart_000_0112_01C911B5.A3594860 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit How did you work out your build problem? Charlie _____ From: Simone Busoli [mailto:[email protected]] Sent: Monday, September 08, 2008 12:29 PM To: Charlie Poole Cc: [email protected] Subject: Re: [Nunit-users] Is.Serializable So here's the patch, for both the BinarySerializable and XmlSerializable constraints. I've followed your guide, I hope I did everything correctly. Feedback welcome. On Sun, Sep 7, 2008 at 7:35 PM, Charlie Poole <[email protected]> wrote: Fair Enough! I'll put it on both lists. Charlie _____ From: [email protected] [mailto:[email protected]] On Behalf Of Simone Busoli Sent: Sunday, September 07, 2008 12:24 AM To: Charlie Poole Cc: [email protected] Subject: Re: [Nunit-users] Is.Serializable Hi Charlie, I'd prefer to work on it again, there's been some changes since I wrote it in the beginning, and it would be useful for me to get comfortable with them. If you agree, I think this would be the right moment to publish the list of steps required to create a new constraint. On Sun, Sep 7, 2008 at 1:33 AM, Charlie Poole <[email protected]> wrote: Hi Simone, I'm now back to looking at this patch, which I set aside while working on other stuff. I agree with you about having two different constraints. Do you want me to put in the patch you sent and change the name to "Binary..." or would you like to rework it? As noted, we do now have a generic AttributeConstraint. Charlie _____ From: Simone Busoli [mailto:[email protected]] Sent: Thursday, August 14, 2008 11:15 AM To: Charlie Poole Cc: [email protected] Subject: Re: [Nunit-users] Is.Serializable To check just for the attribute or the interface Is.Serializable() OR Is.Serializable To check by trying to do it Is.Serializable(formatter) OR Is.Serializable.Using(formatter) I think that making Is.Serializable check for the presence of the attribute on the class might be misleading, because its presence doesn't mean it's serializable, and its absence doesn't mean it isn't. I think that Is.Serializable should be used to check that an object is really serializable, together with its references. That is, Is.Serializable should come in two flavours, one that checks if it is serializable in binary format, and another for xml. I'll come to this later. About checking for the presence of the attribute, as you mentioned in a comment to Fabio's feature request, I think it could be generalized with Has.Attribute<> or Has.Attribute(Type). So, given that the presence of an attribute is checked with a generic Has.Attribute, the way I would tackle the true ability of an object graph to serialize is either using Is.XmlSerializable and Is.BinarySerializable or something equivalent. I don't get how you could pass in an instance of a formatter; I guess you proposed it because you might want to be able to use the assertion for other types of formatters not built into the .net fx s well, but then how would you call their methods? Via reflection? The aternatives above are between using a method and using a property. It would be cool to use the property for te first example and the method for the second, but that's not possible. Most of our syntactic elements use a property format when there is no argument. When an element has an optional argument, then we are forced to use method syntax, which may look a bit odd. For example, we have to use Is.Ordered() rather than Is.Ordered - That example should be familiar to you :-) I lean toward "Using" or "With" or some other keyword. What do folks think? I'm fine with anything you choose. I don't think it's so important if it's a property or a method, just let's try to be consistent :) Charlie _____ From: Simone Busoli [mailto:[email protected]] Sent: Thursday, August 14, 2008 12:16 AM To: Charlie Poole Subject: Re: [Nunit-users] Is.Serializable Hmm, I just realized that what I'm doing is not enough for the object to be serializable. I noticed that the prerequisites for it to be serializable are quite different according to whether you want to serialize it to xml or to binary. For example, the binary serialization doesn't require classes to be public, while xml does. xml serialization doesn't require the serializable attribute, while the binary does. So I'm wondering if it could be the case to split the assertion in IsBinarySerializable and IsXmlSerializable, or check that it is both binary and xml serializable in the same assertion. Thoughts? On Thu, Aug 14, 2008 at 2:02 AM, Charlie Poole <[email protected]> wrote: Hi Simone, This looks good to me. Would you like to synch up and fix it so it works with the latest code? My major changes to Constraint, ConstraintBuilder, etc. are done and it would give you a good way for you to get familiar with those changes. Once it's done, you can either send me a new patch or - if you would like - I'll make you a commiter so you can add it yourself. If you agree, I'll explain more to you about review of code etc. Charlie _____ From: [email protected] [mailto:[email protected]] On Behalf Of Simone Busoli Sent: Monday, August 11, 2008 7:11 AM To: [email protected] Subject: [Nunit-users] Is.Serializable With regards to: http://sourceforge.net/tracker/index.php?func=detail <http://sourceforge.net/tracker/index.php?func=detail&aid=2028517&group_id=1 0749&atid=360749> &aid=2028517&group_id=10749&atid=360749 I have implemented a SerializableConstraint accessible via Is.Serializable. The match is true if serialization to and deserialization from a memory stream via a BinaryFormatter both succeed and the deserialized object is not null. Otherwise the match returns false. ------=_NextPart_000_0112_01C911B5.A3594860 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Dus-ascii"> <META content=3D"MSHTML 6.00.6000.16705" name=3DGENERATOR></HEAD> <BODY> <DIV><SPAN class=3D687291920-08092008><FONT face=3DArial color=3D#0000ff = size=3D2>How=20 did you work out your build problem?</FONT></SPAN></DIV> <DIV><SPAN class=3D687291920-08092008><FONT face=3DArial color=3D#0000ff = size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D687291920-08092008><FONT face=3DArial color=3D#0000ff = size=3D2>Charlie</FONT></SPAN></DIV><BR> <BLOCKQUOTE dir=3Dltr=20 style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px = solid; MARGIN-RIGHT: 0px"> <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft> <HR tabIndex=3D-1> <FONT face=3DTahoma size=3D2><B>From:</B> Simone Busoli=20 [mailto:[email protected]] <BR><B>Sent:</B> Monday, September = 08, 2008=20 12:29 PM<BR><B>To:</B> Charlie Poole<BR><B>Cc:</B>=20 [email protected]<BR><B>Subject:</B> Re: [Nunit-users] = Is.Serializable<BR></FONT><BR></DIV> <DIV></DIV> <DIV dir=3Dltr>So here's the patch, for both the BinarySerializable = and=20 XmlSerializable constraints. I've followed your guide, I hope I did = everything=20 correctly. Feedback welcome.<BR><BR> <DIV class=3Dgmail_quote>On Sun, Sep 7, 2008 at 7:35 PM, Charlie Poole = <SPAN=20 dir=3Dltr><<A=20 = href=3D"mailto:[email protected]">[email protected]</= A>></SPAN>=20 wrote:<BR> <BLOCKQUOTE class=3Dgmail_quote=20 style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: = #ccc 1px solid"> <DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff size=3D2>Fair Enough! = I'll put it on=20 both lists.</FONT></SPAN></DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff = size=3D2></FONT></SPAN> </DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff=20 size=3D2>Charlie</FONT></SPAN></DIV><BR> <BLOCKQUOTE dir=3Dltr=20 style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff = 2px solid; MARGIN-RIGHT: 0px"> <DIV lang=3Den-us dir=3Dltr align=3Dleft> <HR> <FONT face=3DTahoma size=3D2> <DIV class=3DIh2E3d><B>From:</B> <A=20 href=3D"mailto:[email protected]"=20 target=3D_blank>[email protected]</A> = [mailto:<A=20 href=3D"mailto:[email protected]"=20 target=3D_blank>[email protected]</A>] = <B>On Behalf=20 Of </B>Simone Busoli<BR></DIV><B>Sent:</B> Sunday, September 07, = 2008=20 12:24 AM <DIV> <DIV></DIV> <DIV class=3DWj3C7c><BR><B>To:</B> Charlie Poole<BR><B>Cc:</B> <A=20 href=3D"mailto:[email protected]"=20 = target=3D_blank>[email protected]</A><BR><B>Subject:</B> = Re:=20 [Nunit-users] Is.Serializable<BR></DIV></DIV></FONT><BR></DIV> <DIV> <DIV></DIV> <DIV class=3DWj3C7c> <DIV></DIV> <DIV dir=3Dltr>Hi Charlie,=20 <DIV><BR></DIV> <DIV>I'd prefer to work on it again, there's been some changes = since I=20 wrote it in the beginning, and it would be useful for me to get=20 comfortable with them. If you agree, I think this would be the = right=20 moment to publish the list of steps required to create a new=20 constraint.<BR><BR> <DIV class=3Dgmail_quote>On Sun, Sep 7, 2008 at 1:33 AM, Charlie = Poole <SPAN=20 dir=3Dltr><<A href=3D"mailto:[email protected]"=20 target=3D_blank>[email protected]</A>></SPAN> = wrote:<BR> <BLOCKQUOTE class=3Dgmail_quote=20 style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; = BORDER-LEFT: #ccc 1px solid"> <DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff size=3D2>Hi=20 Simone,</FONT></SPAN></DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff=20 size=3D2></FONT></SPAN> </DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff size=3D2>I'm now = back to looking=20 at this patch, which I set aside while working on other=20 stuff.</FONT></SPAN></DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff=20 size=3D2></FONT></SPAN> </DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff size=3D2>I agree = with you about=20 having two different constraints. Do you want me to put=20 in</FONT></SPAN></DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff size=3D2>the patch = you sent and=20 change the name to "Binary..." or would you like to rework=20 it?</FONT></SPAN></DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff=20 size=3D2></FONT></SPAN> </DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff size=3D2>As noted, = we do now=20 have a generic AttributeConstraint.</FONT></SPAN></DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff=20 size=3D2></FONT></SPAN> </DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff=20 size=3D2>Charlie</FONT></SPAN></DIV><BR> <BLOCKQUOTE dir=3Dltr=20 style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: = #0000ff 2px solid; MARGIN-RIGHT: 0px"> <DIV lang=3Den-us dir=3Dltr align=3Dleft> <HR> <FONT face=3DTahoma size=3D2> <DIV><B>From:</B> Simone Busoli [mailto:<A=20 href=3D"mailto:[email protected]"=20 target=3D_blank>[email protected]</A>] = <BR></DIV><B>Sent:</B>=20 Thursday, August 14, 2008 11:15 AM<BR><B>To:</B> Charlie=20 Poole<BR><B>Cc:</B> <A = href=3D"mailto:[email protected]"=20 target=3D_blank>[email protected]</A>=20 <DIV> <DIV></DIV> <DIV><BR><B>Subject:</B> Re: [Nunit-users]=20 Is.Serializable<BR></DIV></DIV></FONT><BR></DIV> <DIV> <DIV></DIV> <DIV> <DIV></DIV> <DIV dir=3Dltr> <DIV class=3Dgmail_quote> <BLOCKQUOTE class=3Dgmail_quote=20 style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; = BORDER-LEFT: rgb(204,204,204) 1px solid"> <DIV><BR> <DIV><SPAN><FONT face=3DArial color=3D#0000ff size=3D2>To = check just for=20 the attribute or the interface</FONT></SPAN></DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff = size=3D2> =20 Is.Serializable() OR</FONT></SPAN></DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff = size=3D2> =20 Is.Serializable</FONT></SPAN></DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff=20 size=3D2></FONT></SPAN> </DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff size=3D2>To = check by trying=20 to do it</FONT></SPAN></DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff = size=3D2> =20 Is.Serializable(formatter) OR</FONT></SPAN></DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff = size=3D2> =20 = Is.Serializable.Using(formatter)</FONT></SPAN></DIV></DIV></BLOCKQUOTE> <DIV><BR>I think that making Is.Serializable check for the = presence of=20 the attribute on the class might be misleading, because its = presence=20 doesn't mean it's serializable, and its absence doesn't mean = it isn't.=20 I think that Is.Serializable should be used to check that an = object is=20 really serializable, together with its references. That is,=20 Is.Serializable should come in two flavours, one that checks = if it is=20 serializable in binary format, and another for xml. I'll come = to this=20 later.<BR>About checking for the presence of the attribute, as = you=20 mentioned in a comment to Fabio's feature request, I think it = could be=20 generalized with Has.Attribute<> or = Has.Attribute(Type).<BR>So,=20 given that the presence of an attribute is checked with a = generic=20 Has.Attribute, the way I would tackle the true ability of an = object=20 graph to serialize is either using Is.XmlSerializable and=20 Is.BinarySerializable or something equivalent. I don't get how = you=20 could pass in an instance of a formatter; I guess you proposed = it=20 because you might want to be able to use the assertion for = other types=20 of formatters not built into the .net fx s well, but then how = would=20 you call their methods? Via reflection?<BR> </DIV> <BLOCKQUOTE class=3Dgmail_quote=20 style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; = BORDER-LEFT: rgb(204,204,204) 1px solid"> <DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff=20 size=3D2></FONT></SPAN></DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff=20 size=3D2></FONT></SPAN> </DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff size=3D2>The = aternatives=20 above are between using a method and using a property. It = would=20 be</FONT></SPAN></DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff size=3D2>cool = to use the=20 property for te first example and the method for the second, = but=20 </FONT></SPAN></DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff = size=3D2>that's not=20 possible.</FONT></SPAN></DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff=20 size=3D2></FONT></SPAN> </DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff size=3D2>Most = of our=20 syntactic elements use a property format when there is no=20 argument.</FONT></SPAN></DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff size=3D2>When = an element has=20 an optional argument, then we are forced to use=20 method</FONT></SPAN></DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff = size=3D2>syntax, which may=20 look a bit odd. For example, we have to = use</FONT></SPAN><SPAN><FONT=20 face=3DArial color=3D#0000ff size=3D2> = Is.Ordered()</FONT></SPAN></DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff = size=3D2>rather than=20 Is.Ordered - That example should be familiar to you=20 :-)</FONT></SPAN></DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff=20 size=3D2></FONT></SPAN> </DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff size=3D2>I = lean toward=20 "Using" or "With" or some other keyword.</FONT></SPAN></DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff=20 size=3D2></FONT></SPAN> </DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff size=3D2>What = do folks=20 think?</FONT></SPAN></DIV></DIV></BLOCKQUOTE> <DIV><BR>I'm fine with anything you choose. I don't think it's = so=20 important if it's a property or a method, just let's try to be = consistent :)<BR> </DIV> <BLOCKQUOTE class=3Dgmail_quote=20 style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; = BORDER-LEFT: rgb(204,204,204) 1px solid"> <DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff=20 size=3D2></FONT></SPAN></DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff=20 size=3D2></FONT></SPAN> </DIV><FONT color=3D#888888> <DIV><SPAN><FONT face=3DArial color=3D#0000ff=20 size=3D2>Charlie</FONT></SPAN></DIV><BR></FONT> <BLOCKQUOTE dir=3Dltr=20 style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: = rgb(0,0,255) 2px solid; MARGIN-RIGHT: 0px"> <DIV> <DIV lang=3Den-us dir=3Dltr align=3Dleft> <HR> <FONT face=3DTahoma size=3D2><B>From:</B> Simone Busoli = [mailto:<A=20 href=3D"mailto:[email protected]"=20 target=3D_blank>[email protected]</A>] = <BR><B>Sent:</B>=20 Thursday, August 14, 2008 12:16 AM<BR><B>To:</B> Charlie=20 Poole<BR><B>Subject:</B> Re: [Nunit-users]=20 Is.Serializable<BR></FONT><BR></DIV> <DIV></DIV></DIV> <DIV> <DIV></DIV> <DIV> <DIV dir=3Dltr>Hmm, I just realized that what I'm doing is = not=20 enough for the object to be serializable. I noticed that = the=20 prerequisites for it to be serializable are quite = different=20 according to whether you want to serialize it to xml or to = binary.=20 For example, the binary serialization doesn't require = classes to=20 be public, while xml does. xml serialization doesn't = require the=20 serializable attribute, while the binary does. So I'm = wondering if=20 it could be the case to split the assertion in=20 IsBinarySerializable and IsXmlSerializable, or check that = it is=20 both binary and xml serializable in the same assertion.=20 Thoughts?<BR><BR> <DIV class=3Dgmail_quote>On Thu, Aug 14, 2008 at 2:02 AM, = Charlie=20 Poole <SPAN dir=3Dltr><<A=20 href=3D"mailto:[email protected]"=20 target=3D_blank>[email protected]</A>></SPAN> = wrote:<BR> <BLOCKQUOTE class=3Dgmail_quote=20 style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; = BORDER-LEFT: rgb(204,204,204) 1px solid"> <DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff = size=3D2>Hi=20 Simone,</FONT></SPAN></DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff=20 size=3D2></FONT></SPAN> </DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff = size=3D2>This looks good=20 to me. Would you like to synch up and fix it so it works = with=20 the latest code? My major</FONT></SPAN></DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff = size=3D2>changes to=20 Constraint, ConstraintBuilder, etc. are done and it = would give=20 you a good way for you</FONT></SPAN></DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff = size=3D2>to get familiar=20 with those changes. Once it's done, you can either send = me a new=20 patch or - if</FONT></SPAN></DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff = size=3D2>you would like=20 - I'll make you a commiter so you can add it yourself. = If you=20 agree, I'll explain more</FONT></SPAN></DIV> <DIV><SPAN><FONT face=3DArial color=3D#0000ff = size=3D2>to you about=20 review of code etc.</FONT></SPAN></DIV> <DIV> </DIV> <DIV><SPAN></SPAN><FONT face=3DArial><FONT = color=3D#0000ff><FONT=20 = size=3D2>C<SPAN>harlie</SPAN></FONT></FONT></FONT><BR></DIV> <BLOCKQUOTE dir=3Dltr=20 style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; = BORDER-LEFT: rgb(0,0,255) 2px solid; MARGIN-RIGHT: 0px"> <DIV lang=3Den-us dir=3Dltr align=3Dleft> <HR> <FONT face=3DTahoma size=3D2><B>From:</B> <A=20 = href=3D"mailto:[email protected]"=20 = target=3D_blank>[email protected]</A>=20 [mailto:<A=20 = href=3D"mailto:[email protected]"=20 = target=3D_blank>[email protected]</A>]=20 <B>On Behalf Of </B>Simone Busoli<BR><B>Sent:</B> = Monday,=20 August 11, 2008 7:11 AM<BR><B>To:</B> <A=20 href=3D"mailto:[email protected]"=20 = target=3D_blank>[email protected]</A><BR><B>Subject:</B> = [Nunit-users] Is.Serializable<BR></FONT><BR></DIV> <DIV> <DIV></DIV> <DIV dir=3Dltr>With regards to: <A=20 = href=3D"http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D= 2028517&group_id=3D10749&atid=3D360749"=20 = target=3D_blank>http://sourceforge.net/tracker/index.php?func=3Ddetail&am= p;aid=3D2028517&group_id=3D10749&atid=3D360749</A><BR><BR>I=20 have implemented a SerializableConstraint accessible = via=20 Is.Serializable. The match is true if serialization to = and=20 deserialization from a memory stream via a = BinaryFormatter=20 both succeed and the deserialized object is not null.=20 Otherwise the match returns=20 = false.<BR></DIV></DIV></BLOCKQUOTE></DIV></BLOCKQUOTE></DIV><BR></DIV></D= IV></DIV></BLOCKQUOTE></DIV></BLOCKQUOTE></DIV><BR></DIV></DIV></DIV></BL= OCKQUOTE></DIV></BLOCKQUOTE></DIV><BR></DIV></DIV></DIV></DIV></BLOCKQUOT= E></DIV></BLOCKQUOTE></DIV><BR></DIV></BLOCKQUOTE></BODY></HTML> ------=_NextPart_000_0112_01C911B5.A3594860-- --===============1669745205== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ --===============1669745205== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Nunit-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nunit-users --===============1669745205==--