Yes it does, Kerry. The slowest part of the whole project is opening the comparison drawing, which is required because there is no way, yet, to access Civil3D objects unless the drawing is open and current. Once the drawing has opened, the data is grabbed, then closed, by the time it finishes closing the form displays. The actual time to populate all 3 treeviews is < 1 second +/- 0.5 second, based on my super accurate eyeball stop watch.
And if you saw the rest of the code you'd be as shocked as I was at how fast it works. I actually use existing code from another part of this project that grabs the Styles and places them into a WPF treeview. I then take THAT data to build my own Lists which I run the comparison on and build the 3 treeviews you see here. This all started with a "I wonder if this could be done" by someone else, so I used what we already had for other things to test it with. Now that I see how quick it is, I'm going to leave it alone for a while.
This was done with 2 drawings, one with about 1500 C3D styles, the second has almost as many, most of which are the same. This means the matching styles is also around 1500. So it's processing 1500 styles 4 times (twice for the WPF control and twice for the lists for treeviews), then the comparison, then the population of the 3 TreeViews.