Hi Bonnie,

>But that's the point ... the .NET CLR will come included with Windows, there will be no reason to download it and install it.

That may work for new workstations but it doesn't address workstations in the field. And actually, with many of my customers, it doesn't work for new workstations either as many of my customers use a single image ("model office") type of install for new workstations to maintain a consistent environment across workstations.

> Besides, the different versions are supposed to be able to co-exist (I had both 1.0 and 1.1 Frameworks on my machine with no problems whatsoever). What issues are you having? Why would an upgrade break other apps? It shouldn't.

I didn't mean to imply there was a problem with 1.0 and 1.1 CLR on the same workstation. I have personally never seen a problem with 1.0 and 1.1 co-existing. What I meant was that the upgrade process to install a fully patched version of .NET on an existing workstation is invasive to the point of breaking other, non .NET applications that have dependencies on certain OS files upgraded during the .NET setup.

I've had good luck with .NET applications on servers. But my personal experience with .NET apps on the client side has been painful. I'm sure that eventually this pain will go away. But right now, for my business, the pain and risks are too great to merit releasing a .NET version of our software for desktop clients.

Malcolm