Subscriber asp.net deployment with .net 3.5SP1
We have an asp.net product that is currently running on the .net 2.0 framework. We are using bootstrapper vs2008 for deployment.
A few months ago I tried to upgrade to .net 3.5SP1 and used the bootloader 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 the user the impression that our program is too slow to install (and also there is no activity on the screen for a while, so they tend to reboot thinking that the machine is stuck!).
I am wondering if anyone has encountered this issue and how they dealt with it. Some things come to my mind.
-
Show splash screen when .net 3.5sp1 is downloaded and installed to let the user know that he is setting up a lot of work on the album and they need to wait! BTW: can this be done with vs .net 2008 deployment project?
-
Don't do any downloads at all, use the launch condition to see if there is a .net 3.5SP1 client on the machine, if yes, just submit them to microsoft site to install and download.
-
Somehow isolate the DLLs that are required from the full 231MB package (or so) and only install the ones that are required. Is it possible?
The "client profile" seems to be of little help to asp.net programs with a user having .net 2.0 on their machine, it just does a full install by default ...
a source to share
Maybe the above link can help you why these strange things are happening.
"Note if you run .NET Framework 3.5 SP1 on a non-English OS! If you run .NET Framework 3.5 SP1 on a non-English OS, it will try to install the .NET Framework 3.5 SP1 language pack in the language that matches the language Default OS: Since the language pack is not part of the complete package, the .NET Framework 3.5 SP1 installer will attempt to download and install it for the user behind the scenes on non-English operating systems. "
And here is the link Deploying .NET Framework 3.5 SP1
a source to share