On Wed, Oct 1, 2008 at 10:36 PM, Dean Brettle <[EMAIL PROTECTED]> wrote:
> I noticed the following difference: > > [mono20] ~/tmp/mywebcontrol @ monodis --assembly > MyWebControlProject.Mono.dll | grep Flags > Flags: 0x00000000 > [mono20] ~/tmp/mywebcontrol @ monodis --assembly > MyWebControlProject.Net.dll | grep Flags > Flags: 0x00000001 > > Since this is a strong-named assembly containing the public key, isn't > 0x00000001 the correct value for Flags? If MS's VB.NET compiler requires > that flag to be set for strong-named assemblies, then that would explain the > problem. > > I'd like to test that hypothesis by changing the Flags value, but I don't > know how to do that off-hand. Using .NET's sn.exe to resign the assembly > built with Mono, didn't change the Flags value. > Adding the following to AssemblyInfo.cs did change Flags to 0x00000001, and DID allow the custom control to be used in a VB.NET Web Application project. [assembly: AssemblyFlags(AssemblyNameFlags.PublicKey)] So, is the fact that this is necessary a bug in mcs, MonoDevelop, or something else? --Dean
_______________________________________________ Mono-devel-list mailing list [email protected] http://lists.ximian.com/mailman/listinfo/mono-devel-list
