[Mono-bugs] [Bug 81446][Nor] New - PrivateBinPath used incorrectly ?

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Tue Apr 24 17:49:48 EDT 2007

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 gert.driesen at pandora.be.


--- shadow/81446	2007-04-24 17:49:48.000000000 -0400
+++ shadow/81446.tmp.25192	2007-04-24 17:49:48.000000000 -0400
@@ -0,0 +1,52 @@
+Bug#: 81446
+Product: Mono: Class Libraries
+Version: 1.2
+OS: All
+OS Details: 
+Status: NEW   
+Priority: Normal
+Component: Sys.Web
+AssignedTo: mhabersack at novell.com                            
+ReportedBy: gert.driesen at pandora.be               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: PrivateBinPath used incorrectly ?
+In System.Web, the PrivateBinPath of the domain is apparently not used 
+First of all, the PrivateBinPath is a list of directories relative to the 
+ApplicationBase of the domain, not an absolute path. 
+Sidenote: According to the .NET SDK, these directories are separated by a 
+semi-colon, but we used Path.PathSeparator instead (although this means 
+configuration files must be modified between platforms). 
+In Mono (Application.CreateApplicationHost), we set the PrivateBinPath to 
+the absolute path of the bin directory (while it should only 
+contain "bin"). Moreover, we never cope with the fact that PrivateBinPath 
+can be a list of subdirectories (of ApplicationBase).
+Also, we manually iterate over assemblies in the privatebinpath to load 
+types while the runtime should take care of this if you use Type.GetType. 
+This should only be necessary if you want to load types from the 
+privatebinpath even if no assembly name is specified in the type name ? 
+Are you sure MS does this ?
+I've also noticed that if you set the privatebinpath in the (runtime 
+section) of the web configuration file, the subdirectories specified are 
+not used to load types in Mono. 
+I have a repro for this, but you need to manually modify the 
+(privatebinpath in the) Web.config file depending on the platform on 
+which you want to run it (because of the difference in path separator).
+I'm not sure if this is something that must be fixed in System.Web, as 
+this may be a runtime issue. Actually, I doubt if this can be fixed in 
+System.Web since the privatebinpath set in the configuration file is not 
+exposed using AppDomainSetup.PrivateBinPath. I'll perform some test 
+in .NET later to verify this.

More information about the mono-bugs mailing list