[Mono-bugs] [Bug 65688][Nor] Changed - Obfuscated code and ActiveReports

[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 vargaz@gmail.com.

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

--- shadow/65688	2004-09-16 10:31:02.000000000 -0400
+++ shadow/65688.tmp.11865	2004-09-16 15:53:40.000000000 -0400
@@ -1,12 +1,12 @@
 Bug#: 65688
 Product: Mono: Runtime
 Version: unspecified
 OS: unknown
 OS Details: fedora 2
-Status: NEEDINFO   
+Status: CLOSED   
 Resolution: 
 Severity: Unknown
 Priority: Normal
 Component: misc
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: lomi@dylog.it               
@@ -133,6 +133,35 @@
 All Classes and Methods in C:\Program Files\Common Files\Data 
 Dynamics\ActiveReports for .NET\ActiveReports.PdfExport.dll Verified
 ---------------------------------------------------------------------
 Sorry, but I cannot ask to the vendor to decrease the level of 
 darkening to make to work the runtime of mono.
 This would increase the risk of reverse engineering.
+
+------- Additional Comments From vargaz@gmail.com  2004-09-16 15:53 -------
+The monodis problem is fixed in CVS. As for the 'unsupported calling
+convention' error: The problem is actuall in ActiveReports.Viewer.dll.
+When running peverify on that file, it reports:
+
+~/active-reports>peverify ActiveReports.Viewer.dll
+
+Microsoft (R) .NET Framework PE Verifier.  Version  2.0.40607.16
+Copyright (C) Microsoft Corporation. All rights reserved.
+
+[MD]: Error: Implementation Map has invalid calling convention 0x0000.
+[token:0x
+00000002]
+[MD]: Error: Implementation Map has invalid calling convention 0x0000.
+[token:0x
+00000003]
+[MD]: Error: Implementation Map has invalid calling convention 0x0000.
+[token:0x
+00000004]
+...
+
+So this is not a valid assembly, and this should be reported to 
+the developers of ActiveReports.
+
+BTW, I'm pretty sure ActiveReports will not run on mono even if this
+is fixed, since it relies on calling Win32 API functions using
+pinvoke, as this example shows.
+