[Mono-devel-list] System.Reflection.AssemblyName issues

[Jackson Harper]

Hi Gert,

	I started to fix this but even with my fix we will get different output
right now, and its not worth introducing allot of logic to fix. Both our
AssemblyName::FullName and MSs AssemblyName::FullName are correct and
its really just a formatting issue. The reason for the difference comes
down to them accessing various properties of an assembly name at
different times then we do. 
 
	File a bug report and mark it as wishlist to be honest it might even
get marked as NOTABUG eventually. I dont anticipate this being fixed for
1.0 as the chances that it would introduce a class lib bug far outweigh
the need to fix it. Unless you have some issue that requires it to be
changed.

Jackson


On Tue, 2004-06-08 at 23:42, Gert Driesen wrote:
> Hi,
> 
> I've noticed that there are some issue with the Mono implementation of
> System.Reflection.AssemblyName, apparently the Mono AssemblyName.FullName
> (and ToString()) always output the Culture=... and PublicKeyToken=... parts
> of the assembly name, regardless of whether a culture of public key has been
> set.
> 
> This code fragment :
> 
>     AssemblyName a = new AssemblyName ();
>     a.Name = "TestAssemblyA";
>     a.Version = new Version(1, 5);
>     Console.WriteLine ("A: " + a.FullName);
> 
> would result in the following output on MS.NET :
> 
>     A: TestAssemblyA, Version=1.5
> 
> While on Mono you'd get :
> 
>     A: TestAssemblyA, Version=1.5, Culture=neutral, PublicKeyToken=null
> 
> I also noticed that there's an issue with Assembly.GetName():
> 
> For this code fragment (executed in a non signed, culture neutral assembly
> called Test) :
> 
>     Console.WriteLine (Assembly.GetExecutingAssembly ().GetName
> (false).FullName);
> 
> I get the following output on MS.NET :
> 
>     test, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null
> 
> While on Mono I get :
> 
>     test, Version=0.0.0.0, Culture=neutral
> 
> Another thing I noticed while looking at the code of AssemblyName, is that
> the serialization stuff is very much incomplete.
> 
> I attached a small test case (not including the serialization issue).
> 
> Haven't had time to look into this much further (duty calls) and can't seem
> to access the Mono website right now, so I can't file a bug report for this
> yet.
> 
> Gert