[Mono-bugs] [Bug 59891][Wis] Changed - AssemblyName.FullName does not match MS.NET

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by echeslack@gmail.com.

http://bugzilla.ximian.com/show_bug.cgi?id=59891

--- shadow/59891	2004-06-09 15:00:04.000000000 -0400
+++ shadow/59891.tmp.26144	2004-07-14 00:58:57.000000000 -0400
@@ -1,14 +1,14 @@
 Bug#: 59891
 Product: Mono: Class Libraries
 Version: unspecified
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Wishlist
 Component: CORLIB
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: gert.driesen@pandora.be               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -36,6 +36,19 @@
 While on Mono you always get a fully qualified assembly name :
 
 A: TestAssemblyA, Version=1.5, Culture=neutral, PublicKeyToken=null
 
 I've committed unit test for this to CVS, see TestFullName[1-8] in  
 MonoTests.System.Reflection.AssemblyNameTest.
+
+------- Additional Comments From echeslack@gmail.com  2004-07-14 00:58 -------
+I'm adding an attachment that fixes all the tests that were failing,
+but then breaks TestFullName1.  Basically instead of always adding
+everything it tries to check if each item has been set.  This works in
+most cases, but is a problem with the Version item.  The default
+constructor leaves major, minor, build, and revision at 0 and the
+version member as null.  However, it seems that in the case given in
+TestFullName1 (int type AssemblyName), the version reference is still
+null so we can't check that, and we also can't check the numbers
+because the default of 0 could be valid for all of them (I think).
+
+Ideas?