Less Than Dot is a community of passionate IT professionals and enthusiasts dedicated to sharing technical knowledge, experience, and assistance. Inside you will find reference materials, interesting technical discussions, and expert tips and commentary. Once you register for an account you will have immediate access to the forums and all past articles and commentaries.
Your profile
Tag cloud
.net .net 3.5 .net 4.0 2003 access modifiers beginners book buildup c# excel f# linq microsoft reporting engine nhibernate nhprof nunit programming reflection reportviewer resharper rhino mocks structuremap threading unit testing vb.net vb.net. visual studio 2010 windows forms windows presentation foundation wpf
Authors
- chrissie1 (122)

- SQLDenis (17)

- Alex Ullrich (8)

- chaospandion (4)

- George Mastros (1)

- chopstik (1)

- tarwn (1)

- remou (1)

- More...
Main Categories
Search
Google Ads
Category: VB.NET
Yesterday I made a post about using a queue instead of a list because the code was so much cleaner. I think it is very important that code is clean and easier to read.
But then Denis asked about the performance differences between the 2 methods. I hadn't worried about the performance, because in my case the performance was good in both cases.
But I aim to please my fellow LTDers, so I did a little performance test. And let me remind you that like most performance tests, this one ...
I was doing this in my code.
When you databind your DataGridView to a List.
Like this.
First I create a class Person so I can bind to that. Watch the default constructor, it needs to make new elements, if that is what you want.
For my usercontrols I tend to use the StructureMap BuildUp feature. I will leave it to the big man himself to introduce you to this feature.
I use property injection in this case because the designer doesn't like usercontrols that have constructors that are not empty, since it will try to execute the code in that constructor. So we revert to property injection and the BuildUp feature....
Yes, I still use svn and yes perhaps I should try that Git thing people keep talking about. But anyway.
Since this post is for my pleasure and my pleasure only I will post a little something to remind me how to solve those tree conflicts. Because I keep forgetting how to do it.
First of all I get a message on commit saying there is a tree conflict.

Than we do an update and forget to take a printscreen.
:: Next >>


LTD Social Sitings
Note: Watch for social icons on posts by your favorite authors to follow their postings on these and other social sites.