Title: RE: [Mono-dev] ConfigurationElementCollection.ThrowOnDuplicate
Hi Atsushi,
Yeah, I'm OK to commit.
Kosta
-Original Message-
From: Atsushi Eno [mailto:[EMAIL PROTECTED]]
Sent: Mon 25/12/2006 18:18
To: Konstantin Triger
Cc: mono-devel-list@lists.ximian.com
Subject: Re:
no [mailto:[EMAIL PROTECTED]
Sent: Fri 22/12/2006 16:09
To: Konstantin Triger
Cc: mono-devel-list@lists.ximian.com
Subject: Re: [Mono-dev] ConfigurationElementCollection.ThrowOnDuplicate
Hi Kosta,
Thanks for the hint :-) Now I understand what ThrowOnDuplicate
means - it rejects a different element. T
Title: RE: [Mono-dev] ConfigurationElementCollection.ThrowOnDuplicate
Hi Atsushi,
I think it should be like this:
protected void BaseAdd (ConfigurationElement element, bool throwIfExists)
{
- if (throwIfExists && BaseIndexOf (elemen
essage-
From: [EMAIL PROTECTED] on behalf of Atsushi Eno
Sent: Fri 22/12/2006 11:03
To: mono-devel-list@lists.ximian.com
Subject: [Mono-dev] ConfigurationElementCollection.ThrowOnDuplicate
Hi,
I have been trying to fix some web service config stuff, and
noticed that ConfigurationElementCollect
Title: RE: [Mono-dev] ConfigurationElementCollection.ThrowOnDuplicate
Hi Atsushi,
I think the implementation of ThrowOnDuplicate is correct: it indicates whether the collection throws if duplicates exist. To make this happen there should be elements with same keys but different values. But
Hi,
I have been trying to fix some web service config stuff, and
noticed that ConfigurationElementCollection.ThrowOnDuplicate property
behavior is somewhat different from .net (the attached example
does not raise an error on .net while mono does).
According to the documentation, I believe that Mo
