Deploying .NET from a CD

[the_grove_man]

I have an application that I am giving to customers from a CD. Using
the setup everything works fine but one thing.

When the customer doesn't have .NET rather than having them go to the
InstallURL in the Launch Conditions I am having them go to
".\dependencies\dotnetfx.exe" which is on my CD and this works fine.
Except after it installs .NET on their machine the user then has to
run the Setup AGAIN to install my Setup.exe. It doen't go directly to
my setup after it installs the .NET framework as it does if I used the
internet link for installing .NET.

Anybody ever come across this and could this be resolved?

(e-mail address removed)
John

 

[Phil Wilson]

I'd use the bootstrapper to install the framework and then run your MSI
file, instead of the download from the MSI (which is what you are doing).
The MSI setup can't reverse itself once it's started.
http://msdn.microsoft.com/msdnmag/issues/04/10/Bootstrapper/

 

[the_grove_man]

I AM using the bootstrap program. The setup program IS A bootstrap
application that opens an MSI Package and installs the application and
its components on the client computer. The CD consists of the following
in the CD root:

1. C5_Setup.msi
2. setup.exe
3. autorun.inf
4. dependencies folder

In the dependencies folder is the following:
1.dotnetfx.exe
2. MDAC_TYP.EXE
3. W2KSP4_EN.EXE
4.WindowsInstaller-KB884016-v2-x86.exe

However, if the customer has .net framework everything installs
correctly. If they do not, it intsalls the .NET framework correctly.
However, after it installs the .net framework it doesn't continue with
the setup.exe, it just hangs. The User has to select the setup.exe
again (If .NET framework was installed first) in order to install the
program

Understand?
John

I'd use the bootstrapper to install the framework and then run your MSI
file, instead of the download from the MSI (which is what you are doing).
The MSI setup can't reverse itself once it's started.
http://msdn.microsoft.com/msdnmag/issues/04/10/Bootstrapper/
--
Phil Wilson [MVP Windows Installer]
----

I have an application that I am giving to customers from a CD. Using
the setup everything works fine but one thing.

When the customer doesn't have .NET rather than having them go to the
InstallURL in the Launch Conditions I am having them go to
".\dependencies\dotnetfx.exe" which is on my CD and this works fine.
Except after it installs .NET on their machine the user then has to
run the Setup AGAIN to install my Setup.exe. It doen't go directly to
my setup after it installs the .NET framework as it does if I used the
internet link for installing .NET.

Anybody ever come across this and could this be resolved?

(e-mail address removed)
John

 

[Phil Wilson]

Let's be precise here - if you are using terms like Launch Condition and
InstallUrl you are not using the bootstrapper prerequisites button that
creates a bootstrapper to install the prerequisites before launching the MSI
file. InstallUrl is a property of the MSI setup's .NET framework launch
condition, not a bootstrapper term. In the setup project, right-click the
project, select properties, click prerequisites, and use those to install
the prerequisites. The behavior of your setup and the terms you're using
imply that you are using a setup.exe to launch the MSI file which fails the
framework installation test, installs the framework and then requires that
you run the setup.exe again (as the messagebox says in this situation). When
I use the *bootstrapper* (as opposed to the MSI launch condition) to
install a dependency it does not require me to rerun setup.exe again.
--
Phil Wilson [MVP Windows Installer]
----

I AM using the bootstrap program. The setup program IS A bootstrap
application that opens an MSI Package and installs the application and
its components on the client computer. The CD consists of the following
in the CD root:

1. C5_Setup.msi
2. setup.exe
3. autorun.inf
4. dependencies folder

In the dependencies folder is the following:
1.dotnetfx.exe
2. MDAC_TYP.EXE
3. W2KSP4_EN.EXE
4.WindowsInstaller-KB884016-v2-x86.exe

However, if the customer has .net framework everything installs
correctly. If they do not, it intsalls the .NET framework correctly.
However, after it installs the .net framework it doesn't continue with
the setup.exe, it just hangs. The User has to select the setup.exe
again (If .NET framework was installed first) in order to install the
program

Understand?
John

I'd use the bootstrapper to install the framework and then run your MSI
file, instead of the download from the MSI (which is what you are doing).
The MSI setup can't reverse itself once it's started.
http://msdn.microsoft.com/msdnmag/issues/04/10/Bootstrapper/
--
Phil Wilson [MVP Windows Installer]
----

I have an application that I am giving to customers from a CD. Using
the setup everything works fine but one thing.

When the customer doesn't have .NET rather than having them go to the
InstallURL in the Launch Conditions I am having them go to
".\dependencies\dotnetfx.exe" which is on my CD and this works fine.
Except after it installs .NET on their machine the user then has to
run the Setup AGAIN to install my Setup.exe. It doen't go directly to
my setup after it installs the .NET framework as it does if I used the
internet link for installing .NET.

Anybody ever come across this and could this be resolved?

(e-mail address removed)
John

 

[the_grove_man]

Phil, thank you for taking the time to review my question. I did use
the bootstrapper button and selected that .NET to be installed from my
location (the CD). Perhaps my problem is I think I used both he MSI
properties and the bootstrapper.

It never fails the installation test. It tests to see if the client
computer has .NET or not. If the User does not have it, it correctly
installs it. If the user has dotnet, it correctly installs the program.

The only issue is if the user doesn't have .net and after it intstalls
it from the CD it fails to go to the setup. I think I used both, the
MSI properties and the bootstrapper.

John

Let's be precise here - if you are using terms like Launch Condition and
InstallUrl you are not using the bootstrapper prerequisites button that
creates a bootstrapper to install the prerequisites before launching the MSI
file. InstallUrl is a property of the MSI setup's .NET framework launch
condition, not a bootstrapper term. In the setup project, right-click the
project, select properties, click prerequisites, and use those to install
the prerequisites. The behavior of your setup and the terms you're using
imply that you are using a setup.exe to launch the MSI file which fails the
framework installation test, installs the framework and then requires that
you run the setup.exe again (as the messagebox says in this situation). When
I use the *bootstrapper* (as opposed to the MSI launch condition) to
install a dependency it does not require me to rerun setup.exe again.
--
Phil Wilson [MVP Windows Installer]
----

I AM using the bootstrap program. The setup program IS A bootstrap
application that opens an MSI Package and installs the application and
its components on the client computer. The CD consists of the following
in the CD root:

1. C5_Setup.msi
2. setup.exe
3. autorun.inf
4. dependencies folder

In the dependencies folder is the following:
1.dotnetfx.exe
2. MDAC_TYP.EXE
3. W2KSP4_EN.EXE
4.WindowsInstaller-KB884016-v2-x86.exe

However, if the customer has .net framework everything installs
correctly. If they do not, it intsalls the .NET framework correctly.
However, after it installs the .net framework it doesn't continue with
the setup.exe, it just hangs. The User has to select the setup.exe
again (If .NET framework was installed first) in order to install the
program

Understand?
John

I'd use the bootstrapper to install the framework and then run your MSI
file, instead of the download from the MSI (which is what you are doing).
The MSI setup can't reverse itself once it's started.
http://msdn.microsoft.com/msdnmag/issues/04/10/Bootstrapper/
--
Phil Wilson [MVP Windows Installer]
----
I have an application that I am giving to customers from a CD. Using
the setup everything works fine but one thing.

When the customer doesn't have .NET rather than having them go to the
InstallURL in the Launch Conditions I am having them go to
".\dependencies\dotnetfx.exe" which is on my CD and this works fine.
Except after it installs .NET on their machine the user then has to
run the Setup AGAIN to install my Setup.exe. It doen't go directly to
my setup after it installs the .NET framework as it does if I used the
internet link for installing .NET.

Anybody ever come across this and could this be resolved?

(e-mail address removed)
John