I 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:
* it's simpler to stick with the original iewebcontrols.msi stuff than the new iewebcontrols.exe with all the problems compiling etc.
* ... but I do need to support DTNF 1.1; I have found the old stuff still seems to work OK?
* installation has to be simple/straightforward for customer; I don't think I want them to have do the iewebcontrols.msi
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?
I'd really appreciate some kind of definitive response, and I think many others would too. This is a nightmare...