<p>I'd love to use WPF for a consumer app. However, some real world tests are not very encouraging. On several high-end computers I've tested, the .NET 3.5 installation has taken 15-20 mins to complete. I've seen reports online mentioning 50 mins.</p>

<p>When Vista marketshare is at 70%, this subject will be moot. Until then, reality is that the majority of consumers are on XP and will need a .NET 3.5 install. Adding 15-20 mins (at best) to the install of a consumer app is simply unacceptable.</p>

<p>1) What the frack is the .NET installer taking so long for?</p>

<p>2) Is there any way to optimize the .NET install?</p>

<p>Oh, and I know about the .NET Client Profile. Doesn't improve the situation much.</p>

Its big.
Using the MS supplied web install is the best cause it only installs what it needs (but thats still big)
Only option is to only detect its not there and warn the user and ask them to install it.  Only the first 3.5 app is affected.  All others will be speedy.
Apparently, all supported OSs will be rolled out to this over time using Windows Update and Services Packs and the like.