We have a asp.net product that currently runs on .net 2.0 framework. We are using the vs2008 bootstrapper for the deployment.
Few months ago I tried to upgrade to .net 3.5SP1 and used the bootstrapper for 3.5SP1. Some of our pilot users complained that it took about 30-45 minutes to download and install the framework. This usually gives an impression to the user that our program itself is too slow to install (and also for sometime there is no activity on the screen, so they tend to reboot thinking that the machine is stuck!).
I am wondering if anybody faced this problem and how they dealt with it. Some things comes to my mind are.
Show a splash screen when .net 3.5sp1 is downloading and installing so that user knows that it installing the big famework and they need to wait! BTW: can this be done using the vs.net 2008 deployment project?
Do not do bootstrapping at all, use a launch condition to find out if .net 3.5SP1 is not in the customer machine, if so, just send them to the microsoft site to install and download.
Somehow isolate the dlls that are required from the full 231MB (or so) package and install only those are required. Is this a possibility?
The "Client Profile" does not seem to help much for asp.net programs with user having .net 2.0 on their machine, it just defaults to full install...