Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / General / August 2006

Tip: Looking for answers? Try searching our database.

Deploying .NET from a CD

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
the_grove_man@yahoo.com - 02 Aug 2006 18:08 GMT
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@yahoo.com
John
Phil Wilson - 02 Aug 2006 18:14 GMT
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/
Signature

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.
[quoted text clipped - 11 lines]
> the_grove_man@yahoo.com
> John
the_grove_man@yahoo.com - 02 Aug 2006 19:08 GMT
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).
[quoted text clipped - 18 lines]
> > the_grove_man@yahoo.com
> > John
Phil Wilson - 02 Aug 2006 22:24 GMT
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.
Signature

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
[quoted text clipped - 44 lines]
>> > the_grove_man@yahoo.com
>> > John
the_grove_man@yahoo.com - 02 Aug 2006 23:27 GMT
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
[quoted text clipped - 59 lines]
> >> > the_grove_man@yahoo.com
> >> > John

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.