[Mono-bugs] [Bug 71887][Wis] Changed - detect .NET binaries and automatically invoke them with mono
Sat, 29 Jan 2005 06:36:19 -0500 (EST)
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 firstname.lastname@example.org.
--- shadow/71887 2005-01-27 17:26:55.000000000 -0500
+++ shadow/71887.tmp.27218 2005-01-29 06:36:19.000000000 -0500
@@ -2,13 +2,13 @@
Product: Mono: Class Libraries
@@ -74,6 +74,20 @@
wants the child process to be executed with a different runtime. One
possibility is a program such as the START.EXE which Win9x is bundled
with; invoking "start WindowTest.exe" is effectively identical to
invoking "WindowTest.exe" directly, and would provide an "escape hatch"
for user code that wanted to bypass common sense. ("START.EXE", which the
FileName property would point at, would not be detected as a .NET binary.)
+------- Additional Comments From email@example.com 2005-01-29 06:36 -------
+I don't think user applications ALWAYS expect to run ANY managed code
+application with Mono, especially when we use mono on Windows.
+On Linux, you can use binfmt configuration on your machine and then
+"mono blahblah.exe" will not be required.
+"Question: Can I run Mono applications without using 'mono program.exe'?"
+"Binary compatibility" depends on users code. For example, ".NET on
+windows" developers often specify case-insensitive filenames. It's not
+our blame, but those developers. Our managed code runs programs as
+users wrote to do so. It is the "binary compatibility".