[Mono-bugs] [Bug 73679][Wis] Changed - Class SqlError remoting problem

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

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

--- shadow/73679	2005-04-13 06:41:09.000000000 -0400
+++ shadow/73679.tmp.27675	2005-04-13 08:41:08.000000000 -0400
@@ -86,6 +86,26 @@
 From the exception it seems it is trying to find method 
 System.Data.SqlClient.Error.
 
 adding a public property Error to SqlError will not solve the issue?
 
 can you give me a sample program for this ?
+
+------- Additional Comments From dezelin@gmail.com  2005-04-13 08:41 -------
+Yes, I do understand the whole matter. But this tiny fix that extends
+the remoting compatibility makes no harm to Mono. It makes a financial
+application written in c# for .net that I'm currently working on to
+work on Mono as a hosting platform for our middle tier.
+
+I'm just pointing out that we should make Mono's .NET compatibility
+stack as compatible with .Net as possible, not 100%. Why do we call it
+"compatibility stack"? If we don't need it, why do we have it? Why do
+we want Managed Windows Forms? We could design a much better GUI
+toolkit than SWF is also in 100% c# code! Don't tell me that SWF is
+well designed toolkit. It is designed to have it's application on
+Windows with their bloated, creepy, 10 years old controls.
+
+p.s.
+Just apply that patch and it will work, I've tested it.
+
+Cheers,
+Aleksandar Dezelin