Comments on: Build vs. Buy and Asp.net Server Controls http://thesherpaproject.com/2005/07/17/build-vs-buy-and-aspnet-server-controls/ Thoughts by Ben Carey Tue, 06 Jan 2009 09:42:53 +0000 http://wordpress.org/?v=2.6 By: Austin http://thesherpaproject.com/2005/07/17/build-vs-buy-and-aspnet-server-controls/#comment-10 Austin Mon, 06 Mar 2006 01:44:10 +0000 http://www.thesherpaproject.com/?p=16#comment-10 The only problem with utilizing third party components is that you are now dependent on the third party for support, updates and fixes. Which may or may not come during your project timelines. Even though I agree you should always look at the buy vs. build, I just want to make sure that if I buy then the company I purchase from has a good rep around supporting thier product and response times are fast. The only problem with utilizing third party components is that you are now dependent on the third party for support, updates and fixes. Which may or may not come during your project timelines.

Even though I agree you should always look at the buy vs. build, I just want to make sure that if I buy then the company I purchase from has a good rep around supporting thier product and response times are fast.

]]> By: Dave http://thesherpaproject.com/2005/07/17/build-vs-buy-and-aspnet-server-controls/#comment-9 Dave Mon, 06 Mar 2006 01:43:33 +0000 http://www.thesherpaproject.com/?p=16#comment-9 There's several control suites out there, just depends on what types of controls youre looking for. For UI stuff, there's Infragistics, Syncfusion, DotNetMagic, Xceed, and ComponentArt (but I'm guessing you already know about those :-) There’s several control suites out there, just depends on what types of controls youre looking for. For UI stuff, there’s Infragistics, Syncfusion, DotNetMagic, Xceed, and ComponentArt (but I’m guessing you already know about those :-)

]]>