Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
.NET loop on install
0 views
Skip to first unread message
Eddy Jones
Dec 19, 2002, 8:09:32 PM12/19/02
to
I have an Installshield installation that requires .NET. I include the .NET
platform with the install and it launches installs .NET but doesn't bother
to tell Installshield that it is finished. So, IS continues showing a nice
little progress bar that continually goes from 0 to 100%, over and over
again.
platform with the install and it launches installs .NET but doesn't bother
to tell Installshield that it is finished. So, IS continues showing a nice
little progress bar that continually goes from 0 to 100%, over and over
again.
Has anyone seen this problem before, and if so, were you able to solve it?
Eddy
Phil Wilson
Dec 20, 2002, 2:29:23 PM12/20/02
to
When you say you include the .NET platform, what exactly are you doing? If you're firing off the
dotnetfx.exe with a custom action, you can ask it to wait until it's finished, so this is stuff that
should be under your control. Details Details!!!
dotnetfx.exe with a custom action, you can ask it to wait until it's finished, so this is stuff that
should be under your control. Details Details!!!
"Eddy Jones" <ed...@posortho.com> wrote in message news:efxhxO8pCHA.1988@TK2MSFTNGP09...
Eddy Jones
Dec 23, 2002, 1:00:15 PM12/23/02
to
In Installshield Developer 8.0 and 7.0.
Including .NET involves placing a checkmark in the release manager that
states you want to include .NET. Very little control at this point.
"Phil Wilson" <phil....@unisys.spamcom> wrote in message
news:#SrJY4FqCHA.1628@TK2MSFTNGP12...
Phil Wilson
Jan 6, 2003, 2:55:44 PM1/6/03
to
The difficulty with this helpful InstallShield stuff is that it hides what's really going on. It's
best for you to arrange for the user to run the dotnetfx.exe program to install the runtime, plus
add the runtime service packs if the .NET app requires them to run. It'll get more complicated when
the next
version of the framework comes out, when you'll need to match the framework with your app. In
addition, the runtime has prerequisites of its own, and I've no idea what InstallShield Developer
would do to deal with them.
best for you to arrange for the user to run the dotnetfx.exe program to install the runtime, plus
add the runtime service packs if the .NET app requires them to run. It'll get more complicated when
the next
version of the framework comes out, when you'll need to match the framework with your app. In
addition, the runtime has prerequisites of its own, and I've no idea what InstallShield Developer
would do to deal with them.
Watch for wrap:
http://msdn.microsoft.com/library/en-us/dnnetdep/html/NETFx1Redistreq.asp?frame=true
"Eddy Jones" <ed...@posortho.com> wrote in message news:eSo2jxqqCHA.2484@TK2MSFTNGP10...
0 new messages