[Mono-bugs] [Bug 68836][Wis] New - AssemblyName.FullName gives different result than msft

[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 bmaurer@users.sf.net.

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

--- shadow/68836	2004-10-26 23:05:56.000000000 -0400
+++ shadow/68836.tmp.23915	2004-10-26 23:05:56.000000000 -0400
@@ -0,0 +1,40 @@
+Bug#: 68836
+Product: Mono: Class Libraries
+Version: unspecified
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Wishlist
+Component: CORLIB
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: bmaurer@users.sf.net               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: AssemblyName.FullName gives different result than msft
+
+Doing:
+
+using System;
+using System.Reflection;
+class X {
+	static void Main () {
+		AssemblyName an = new AssemblyName ();
+		an.Name = "x";
+		Console.WriteLine (an.FullName);
+	}
+}
+
+Gives
+x, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null
+
+in msft you just get x.
+
+The problem is we do not differentiate between something not having been
+set and it being 0.0.0.0, neutral, null, etc. The last two are easy to
+solve. Version is a bit harder. In icall.c we set a few int fields as an
+easy way to set the version from native code. So we cant tell if the
+version is really 0.0.0.0 or if it is not set.