We had some bad experiences with 3th party controls, and removing them from
the entire application was a nightmare. So, we dont want to adopt any
control before we know all about it. I think alot of companies have that
kind of problems in the past, and would like to see some realistic data on
the pro's and con's.

At the URL:
http://msdn.microsoft.com/downloads/default.asp?url=/downloads/samples/inter
net/ASP_DOT_NET_ServerControls/WebControls/default.asp
<http://msdn.microsoft.com/downloads/default.asp?url=/downloads/samples/inte
rnet/ASP_DOT_NET_ServerControls/WebControls/default.asp> , you can download
additional Server-side Webcontrols from MSDN (Microsoft(r) Internet Explorer
WebControls Version 1.0 of the ASP.NET Server Controls). 
Since Microsoft sounds safe as a control provider, (and it is for free - as
for as I know =) ) we think we can use them, but some lines in the online
manual gives me the creeps:
This product is only compatible with machines running builds of the .NET
Framework (1.0.3705.0) and Visual Studio(r) .NET (7.0.9466).
Microsoft(r) Internet Explorer WebControls may be downloaded; however, they
are not currently supported. Additionally, the localized versions of
Internet Explorer WebControls are not currently supported and are
unavailable for downloading.
Dont know for sure, what the consequences are of those lines, but before we
get into problems -again- i would like to know more, like:
*	The product is compatible with specific vesions of the .NET
framework and VS.NET. Does that mean that future releases of the .NET
framework/VS.NET can be a problem when using this version of the webcontrols
or just the older (beta) versions? Is it upwards compatible??
*	Are the controls updated on a regular base?
*	"Currently not supported" - when will they be supported?
*	Do we have to pay in the future?
*	Can we integrate and sell the controls with our products?
*	Do we have to install stuff on the client?
*	Can we use the MSI a subset of our applications MSI? (is it a Merge
Module MSI?)
*	Can we detect if the control is installed or can our MSI check for
its existance?
*	Anybody has some bad experiences at using them (like
bugs/installation errors/problems/performance)?
*	Anything else I have missed??

Can anyone help me get rid of some bad feelings about the webcontrols, or
perhaps name some disadvantages that we can take in consideration??

Thanx in advance for any reactions!

Arjen Oetomo