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

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

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

--- shadow/80305	2006-12-18 13:09:26.000000000 -0500
+++ shadow/80305.tmp.24749	2006-12-18 13:34:24.000000000 -0500
@@ -1,14 +1,14 @@
 Bug#: 80305
 Product: Mono: Compilers
 Version: 1.2
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Normal
 Component: C#
 AssignedTo: rharinath at novell.com                            
 ReportedBy: tml at novell.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
@@ -29,6 +29,15 @@
 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.
+
+------- Additional Comments From tml at novell.com  2006-12-18 13:34 -------
+If one has an app.exe.config file (so that one can specify the
+supportedRuntime elements) when running mkbundle2, it indeed says that
+it uses that config file. And the main.c that mkbundle2 creates does
+call mono_register_config_for_assembly(). But the code in
+mono/mono/metadata/domain.c that looks for config files for the exe
+assembly apparently doesn't bother to check for bundled configs, it
+only looks in the file system.