Your code does not verify that your change must be correct. It just shows the fact that it *affects* on our ASP.NET behavior (Or is that a general way for .NET developers to identify the source of bugs?). What I expected was rather like below:
using System; using System.Collections.Specialized; using System.Configuration.Provider; public class MyProvider : ProviderBase { public static void Main () { NameValueCollection config = new NameValueCollection (); config ["name"] = "Name"; config ["description"] = "DESC"; config ["foo"] = "FOO"; Console.WriteLine (config ["description"]); MyProvider p = new MyProvider (); p.Initialize ("Foo", config); Console.WriteLine (config ["name"]); Console.WriteLine (config ["description"]); Console.WriteLine (config ["foo"]); Console.WriteLine ("{0} {1}", p.Name, p.Description); } } Yes, you were right, this test shows how funny behavior .net does. Atsushi Eno John Anderson wrote: > > > On 8/31/07, *John Anderson* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> > wrote: > > On 8/31/07, *Atsushi Eno* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Hmm, I doubt. Your change looks strange (don't you think so? ;-) > Please provide verifiable test case that exactly shows the > behavioral difference. > I'd rather think there is something else to fix (if any). > > > I've attached a smaller test case that will run on ms.net > <http://ms.net> but fails on mono without my patch. > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list