[Mono-bugs] [Bug 675464] New: Runtime should support "long form" signatures for .NET 1.1 assemblies

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=675464

https://bugzilla.novell.com/show_bug.cgi?id=675464#c0


           Summary: Runtime should support "long form" signatures for .NET
                    1.1 assemblies
    Classification: Mono
           Product: Mono: Runtime
           Version: 2.10.x
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: misc
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: jeroen at sumatra.nl
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


Created an attachment (id=416448)
 --> (http://bugzilla.novell.com/attachment.cgi?id=416448)
Repro

User-Agent:       Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64;
Trident/5.0)

NET 1.1 had a Reflection.Emit bug that caused it to use "long form" signatures
for string[] and object[] (e.g. SZARRAY CLASS <System.String> instead of
SZARRAY STRING) and Mono previously supported this (presumably when running
under the 1.1 profile), with 2.10 the 1.1. profile is gone so this code is
starting to fail, but it shouldn't (.NET 2.0 and up accept it as well).

Note that .NET 2.0 appears to accept the long forms even for 2.0 assemblies.

Reproducible: Always

Steps to Reproduce:
Run attached exe with Mono 2.10.
Actual Results:  
WARNING: The runtime version supported by this application is unavailable.
Using default runtime: v2.0.50727

Unhandled Exception: System.TypeLoadException: Could not load type 'Typespec
0x1b000001'.

Expected Results:  
WARNING: The runtime version supported by this application is unavailable.
Using default runtime: v2.0.50727


This breaks older (.NET 1.1 based) IKVM.NET applications.

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.