I actually like the PowerCollections a lot and do not reject it at all. I
don't know where you got that impression ?! The only change I would do is
split up the Algorithms class. It takes already a long time
to find the method you need and on some slower machines, it slows down VS to
a crawl when I
> My business need is building an open source collection component. I will
> use it for in my own software once it is stabilized.
Sounds interesting... any reason not to just use PowerCollections? I
understand wanting to build your own to learn... but do you have a
reason to reject a very good li
On 7/28/07, Brady Kelly <[EMAIL PROTECTED]> wrote:
> I have a little utility to show the ADO Data Link Properties dialogue for
> editing connection strings. I've just moved all the code out of the
> original WinForms test project into a class library, as my code has nothing
> to do with any .NET U
I have a little utility to show the ADO Data Link Properties dialogue for
editing connection strings. I've just moved all the code out of the
original WinForms test project into a class library, as my code has nothing
to do with any .NET UI, but I've come short with the owner parameter I need
to p
