http://forums.asp.net/91.aspxGeneral discussion of the Internet Explorer Web Controls source package for ASP.NET 1.x.enCommunityServer 2007 SP1 (Build: 20510.895)http://forums.asp.net/thread/410069.aspxThu, 04 Dec 2003 15:14:27 GMT4c671506-2930-414c-a40b-8bf57ded5924:410069kevin_joneskevin_jones0http://forums.asp.net/thread/410069.aspxhttp://forums.asp.net/commentrss.aspx?SectionID=91&PostID=410069If anyone knows the answer to this, I would like to know too.http://forums.asp.net/thread/215315.aspxFri, 09 May 2003 14:56:58 GMT4c671506-2930-414c-a40b-8bf57ded5924:215315jonbravejonbrave0http://forums.asp.net/thread/215315.aspxhttp://forums.asp.net/commentrss.aspx?SectionID=91&PostID=215315I have read lots of posts about the current probs with IEWCs. Unfortunately we really seem to need the TreeView (could proably manage without the others). Forget about compiling/using for development. I would like a definitive answer about how we are supposed to install/deploy/distribute to customers. As far as I can see: <br /> <br /> * it's simpler to stick with the original iewebcontrols.msi stuff than the new iewebcontrols.exe with all the problems compiling etc. <br /> <br /> * ... but I do need to support DTNF 1.1; I have found the old stuff still seems to work OK? <br /> <br /> * installation has to be simple/straightforward for customer; I don't think I want them to have do the iewebcontrols.msi <br /> <br /> I am happy to include WebControls.dll in my app's bin directory. From what I have read here, I should be able to include .htcs in my app's area and change web.config to use that, thus avoiding problem of installing outside my app's area. That seemed to work when I tested on someone. But I'm concerned: doesn't the iewebcontrols.msi also do stuff like registry/gac? Is this important/compulsory? <br /> <br /> I'd really appreciate some kind of definitive response, and I think many others would too. This is a nightmare...