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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=81781 --- shadow/81781 2007-06-04 16:30:03.000000000 -0400 +++ shadow/81781.tmp.25735 2007-06-05 10:57:22.000000000 -0400 @@ -921,6 +921,35 @@ related to CreateObject function in our Printing namespace. Tomorrow, I will remove Microsoft.VisualBasic references, compile and tomorrow to see if it eliminates the runtime error. + +------- Additional Comments From [EMAIL PROTECTED] 2007-06-05 10:57 ------- +Removed my Assembliy's references to Microsoft.VisualBasic. Made 10 +code changes that replaced ChrW() and FileLen() with functionality +supplied by the System.IO.FileInfo and System.Char. I built my +application, deployed it and removed the VisualBasic.Dll from the +applications bin folder. + +Application seems to work fine now. Here are a few observations and +speculations. + + +- Sigabrt was caused by the following line of code : + C.Parameters(_messageParam).Value = d.RoutingInformation.MessageId + +- the above line of code uses late binding as collection returns +Object [IDataParam is the underlying type] + +- How does the JIT accomplish this late binding? Why was it Loading +and reflecting on the VisualBasic.dll + +If I get a chance I will create a simple test project and stick the +VisualBasic.Dll in the bin folder to see if failure occurs when late +binding is resolved. + + +Hope this helps. + + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
