Deploying .NET from a CD

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • the_grove_man@yahoo.com
    #1

    Deploying .NET from a CD

    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?

    the_grove_man@y ahoo.com
    John

    Tags: None
    • Phil Wilson
      #2
      Re: Deploying .NET from a CD

      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.
      Microsoft Learn: Build with answers in reach
      http://msdn.microsoft.com/msdnmag/issues/04/10/Bootstrapper/
      Find official documentation, practical know-how, and expert guidance for builders working and troubleshooting in Microsoft products.

      --
      Phil Wilson [MVP Windows Installer]
      ----
      <the_grove_man@ yahoo.comwrote in message
      news:1154538533 .142254.175670@ h48g2000cwc.goo glegroups.com.. .
      >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?
      >
      the_grove_man@y ahoo.com
      John
      >

        Comment

        • the_grove_man@yahoo.com
          #3
          Re: Deploying .NET from a CD

          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.WindowsInstal ler-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


          Phil Wilson wrote:
          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.
          Microsoft Learn: Build with answers in reach
          http://msdn.microsoft.com/msdnmag/issues/04/10/Bootstrapper/
          Find official documentation, practical know-how, and expert guidance for builders working and troubleshooting in Microsoft products.

          --
          Phil Wilson [MVP Windows Installer]
          ----
          <the_grove_man@ yahoo.comwrote in message
          news:1154538533 .142254.175670@ h48g2000cwc.goo glegroups.com.. .
          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?

          the_grove_man@y ahoo.com
          John

            Comment

            • Phil Wilson
              #4
              Re: Deploying .NET from a CD

              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]
              ----
              <the_grove_man@ yahoo.comwrote in message
              news:1154542118 .398445.50260@i 3g2000cwc.googl egroups.com...
              >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.WindowsInstal ler-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
              >
              >
              Phil Wilson wrote:
              >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/is.../Bootstrapper/
              >--
              >Phil Wilson [MVP Windows Installer]
              >----
              ><the_grove_man @yahoo.comwrote in message
              >news:115453853 3.142254.175670 @h48g2000cwc.go oglegroups.com. ..
              >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?
              >
              the_grove_man@y ahoo.com
              John
              >
              >

                Comment

                • the_grove_man@yahoo.com
                  #5
                  Re: Deploying .NET from a CD


                  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

                  Phil Wilson wrote:
                  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]
                  ----
                  <the_grove_man@ yahoo.comwrote in message
                  news:1154542118 .398445.50260@i 3g2000cwc.googl egroups.com...
                  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.WindowsInstal ler-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


                  Phil Wilson wrote:
                  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.
                  Microsoft Learn: Build with answers in reach
                  http://msdn.microsoft.com/msdnmag/issues/04/10/Bootstrapper/
                  Find official documentation, practical know-how, and expert guidance for builders working and troubleshooting in Microsoft products.

                  --
                  Phil Wilson [MVP Windows Installer]
                  ----
                  <the_grove_man@ yahoo.comwrote in message
                  news:1154538533 .142254.175670@ h48g2000cwc.goo glegroups.com.. .
                  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?

                  the_grove_man@y ahoo.com
                  John

                    Comment

                    Previous template Next
                    Working...