In deploying an application with clickonce to a client with .Net framework 1.1 the user is prompted on the install page for the prequisite to install the .Net Framework 2.0. The framework goes through the setup process and appears to install successfully but the application does not install.
If the user reboots the machine and then goes back to the install page it does not prompt for the framework and then installs the application just fine.
I have noticed that this only happens the very first time the 2.0 framework is installed. If I remove the 2.0 framework and go back to the install page it installs the framewok and the application without a reboot.
Does installing the framework the first time on a machine require a reboot If so why is the user not prompted to reboot Is there a way to prompt for a reboot
TIA,
Tim
ClickOnce Deployment on Clients with Framework 1.1
Rob Targosz
We should be rebooting only if necessary. There are return codes from the .NET Fx to indicate that a reboot is needed, and we reboot if we get one of those codes.
We'll take a closer look at the specifics of this scenario and see what we can find out. It's not a known issue.
penyaskito
That explains the mystery I've been having with ClickOnce. Some of my tests require a retry of the application install after Net2.0 was installed while others don't. I didn't need to reboot though, just rerunning the ClickOnce did the trick. The common factor is that the ones that failed were the first install of Net 2.0. In those cases Net 1.1 was on the system as well.
/peter
marek.dziedzic
Sorry about not getting back to this sooner. Was OOF for a few weeks...but have not forgotten about this issue.
At this point for our current users, what I have to suggest is to add to your published page information regarding the possibility that the setup may not finish if 1.1 is already installed...and directing the users to close IE and re-open the publish page again and click to install (not ideal). The bug that we have tracking this issue is currently being looked at for our current product cycle. If/when we have a solution, again I will try to get that posted out here.
The core problem here is when we start the 2.0 install from within the IE shell when 1.1 is already installed, the IE process remains attached in memory to the mscoree that was currently installed with 1.1. Once we finish the 2.0 install and move on to the actual app install at this point, we still have in memory the 1.1 version of mscoree and our 2.0 apps need to use the 2.0 version of mscoree to successfully install. That is why closing IE which releases in-memory mscoree.dll and returning to the publish page works.
-Robert Schoen (Microsoft Visual Basic QA)
JohnyHandSome
I will update my install istructions and await a fix to ClickOnce.
Nikhil Khandelwal - MSFT
I took a look at this yesterday and today and can repro it just as mentioned in this thread. We are still investigating. But in short a reboot is not required. I reviewed the pending reboot table and found no entries that would trigger a reboot return code from the 2.0 framework install...so that is why there is no reboot prompt.
If after completing the 2.0 framework install you open a fresh IE page to the publish site you should be able to install the application.
I will try to post to this thread again once we have something to pass along!
Thanks for posting this issue!
-Robert Schoen (Microsoft Visual Basic QA)
Enkore
I am glad that you are looking into the issue. We will just have to put instructions on the publish.htm page to let them know what to do and then put up with the feedback of why is it called ClickOnce when I have to click twice
!
Thanks,
Tim