When it comes to development tools there are two camps.
Camp One builds everything by hand. They subscribe to the philosophy of "If it's Not Built Here, I ain't gonna use it!"
Camp Two leverages third party tools.
I used to be in Camp One, many years ago. Except for a few FoxPro tools I had used in the early 90's, I had always created everything I needed by hand. Not until I worked for a short while at Synergy Software, a company that was rewriting it's VB3-with-an-Access-backend application to be a VB6-with-SQL Server-backend application. (It was painful to see .NET start to show it's face in 2000 when we were well into the new application.) These guys used a number of third party components and had to work to convince me to use them in the UIs I was building. They used a lot of the FarPoint and Sheridan (now Infragistics) tools.
I quickly learned what fool I had been and now I have my feet well planted in Camp Two. I use third party tools throughout my still existing VB6 apps and in all of my .NET applications. Some critical tools for my VB6 apps were not only controls I could drop on my screen but components, such as Chant's Speechkit which, at that time, was the best way to do TexttoSpeech.
These days I have a slew of diverse third party controls in my apps. Although many companies make large suites of tools, I seem to pick and choose from among them, so I have apps that have Janus, Infragistics and telerik controls all in the same solution. Those are three heavy competitors, but they all get along just fine in my apps. I still use Crystal Reports for my Winforms apps and found one of XCeed's many streaming components to be the perfect solution for compressing web service messages.
Sometimes people have a really hard time trusting something that they didn't build themselves or if they are using an IDE such as Visual Studio, they will only use components that come out of the box. What they don't seem to consider is that companies like Infragistics (who has over 110 employees!) have many developers working on these tools. Some may be smaller, such as SourceGear, but equally high quality. They work very closely with Microsoft and often incorporate better architecture and coding practices than a good percentage of development shops out in the world. And to top it off, they have thousands upon thousands of users constantly giving feedback on these products, so they are continually getting tweaked, improved upon and added to.
Another reason developers avoid 3rd party products is that they are being too penny-wise and pound foolish to see the value of forking out a few hundred dollars and would prefer spending countless hours building something that will potentially not be as high quality as the tools they can buy. Crazy.
Certainly there are lots of tools out there that don't have the backing of a full development team. Peter Blum is an example of a very successful version of this. Peter has focused on security tools and his products constantly receive high praise from developers as well as the security wonks and he has been awarded aspnetPRO Magazine Reader's Choice awards three years in a row as proof.
So if you have been one of the "Not Built Here" kinda coders, I suggest that you rethink your strategy and start taking a look at the incredibly array of tools out there, whether you are coding in .NET or another platform.