[Mono-bugs] [Bug 58922][Maj] Changed - wrong usage of AppDomainSetup.PrivateBinPath when searching for private assemblies, wrong implementation of AppDomain.AppendPrivatePath()

[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 robik@mailbox.sk.

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

--- shadow/58922	2004-05-27 22:05:10.000000000 -0400
+++ shadow/58922.tmp.8041	2004-05-28 04:04:18.000000000 -0400
@@ -99,6 +99,39 @@
 
 ------- Additional Comments From gonzalo@ximian.com  2004-05-27 22:02 -------
 As the test demonstrates, this is not a bug.
 
 ------- Additional Comments From gonzalo@ximian.com  2004-05-27 22:05 -------
 Oh, for the 'btw' it's already filed as bug 57710.
+
+------- Additional Comments From robik@mailbox.sk  2004-05-28 04:04 -------
+Hi Gonzalo!
+
+Sorry for not included a test case. Did you looked at the link i 
+posted at the beginning?
+You say i should use PathSeparator, but MSDN documantation says:
+
+<snip>
+
+AppDomainSetup.PrivateBinPath Property
+Gets or sets the list of directories that is combined with the 
+ApplicationBase directory to probe for private assemblies.
+
+[C#]
+public virtual string PrivateBinPath {get; set;}
+
+Property Value
+A String containing a list of directory names, where each name is 
+separated by a semicolon.
+
+</snip>
+
+it says "semicolon" not "PathSeparator"...
+
+Well, if this is no bug, then it is an incompability between ms.net 
+and mono.
+You have the same issue, when u use an configuration file.
+see: http://bugzilla.ximian.com/show_bug.cgi?id=57612
+
+
+
+