[Mono-bugs] [Bug 80305][Nor] New - Bundled executable looks for machine.config in wrong place

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Mon Dec 18 13:09:26 EST 2006

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 tml at novell.com.


--- shadow/80305	2006-12-18 13:09:26.000000000 -0500
+++ shadow/80305.tmp.23556	2006-12-18 13:09:26.000000000 -0500
@@ -0,0 +1,34 @@
+Bug#: 80305
+Product: Mono: Compilers
+Version: 1.2
+OS Details: 
+Status: NEW   
+Priority: Normal
+Component: C#
+AssignedTo: rharinath at novell.com                            
+ReportedBy: tml at novell.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: Bundled executable looks for machine.config in wrong place
+When building a bundled executable with mkbudle2, the resulting executable
+will look for either mono/1.0/machine.config or mono/2.0/machine.config
+under the directory pointed to by the MONO_CFG_DIR depending on whether it
+happens to find the start assembly (built for 2.0) in the file system or not.
+If it finds the start assembly in the file system, it looks what runtime
+version that assembly wants, and uses that. Otherwise it uses 1.0.
+In my opinion a bundled executable should always use the bundled
+assemblies, never load a version from the file system. Otherwise one will
+easily run into a problem, like I did, that is very hard to diagnose, when
+things work differently in the work directory where the corresponding
+assembly .exe happens to be, and in some other directory.
+Also, I guess I would like mkbundle2 to be enahnced so that the bundled
+mono would know that the default runtime version should be 2.0, not 1.0.

More information about the mono-bugs mailing list