none
J# 2.0 bootstrapper RRS feed

  • Question

  • Hi;

    How do we get the bootstrapper to install J# 2.0 - and to install the correct machine type (32-bit, 64-bit or IA)? At present it installs J# 1.0 - which is 32-bit only.

    What we need it to do:

    1) See if J# is already installed (usually it is).

    2) If not, then download and install with no need for the user to do anything.

    3) If it is an older version of J#, uninstalls it and installs the newer one (J# requires that installation approach).

    How can we get this?

    thanks - dave


    Cubicle Wars - http://www.windwardreports.com/film.htm
    Monday, November 10, 2008 10:49 PM

Answers


  • Hi Dave,

    Not sure the J# 2.0 package will remove the previous version automatically, if it doesn't, you can write you own program to do the stuff like the SQL Express SP 2 does. For more information, please check:

    https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2851359&SiteID=1

    DavidThi808 said:

    How do we, in the bootstrapper, determine is we are 32-bit, 64-bit, or IA-64 and then install the correct version based on that?

    I would like to you create different package for different platform. This is easy to achieve.

    Thanks,
    Rong-Chun Zhang





    Please mark the replies as answers if they help and unmark if they don't.
    Tuesday, November 18, 2008 9:44 AM

All replies


  • Hi Dave,

    If you use Visual Studio 2005, the bootstrapper package for J# .Net 2.0 is already, you can choose it as the prerequisite of your setup project or ClickOnce application. Then when you install the application, it will check if the client machine has installed the J# .Net 2.0 and decide whether to install or not.

    If you didn't find that prerequisite, you still can add your own prerequisite. Please refer the following article to add custom prerequisite:

    http://msdn.microsoft.com/en-us/library/ms165429.aspx

    I also the following tool which may help you to generate the manifest for the prerequisite.

    http://code.msdn.microsoft.com/bmg

    By the way, J# .Net 2.0 is a 32-bit only release. On 64-bit systems, it will execute in the Windows-On-Windows environment.

    Thanks,
    Rong-Chun Zhang

    Please mark the replies as answers if they help and unmark if they don't.
    Thursday, November 13, 2008 6:04 AM
  • Hi;

    Please take a look at http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=1616307&SiteID=1 - the J# 2.0 Second Edition has a 64-bit version. We need the bootstrapper to install that on 64-bit systems. (It's almost like Microsoft wants Vista to fail - supporting 32-bit but not 64-bit.)

    As to the Bootstrapper Manifest Generator, yes we tried that - never got it to work right. Has any group outside of Microsoft ever successfully created their own bootstrapper? If so, we can try again but I don't want to try if everyone else is still failing also.

    thanks - dave
    Cubicle Wars - http://www.windwardreports.com/film.htm
    Thursday, November 13, 2008 4:14 PM

  • Hi Dave,

    Sorry for the previous reply is not very clear, I'd say that the standard J# .Net prerequisite is 32-bit release. Again sorry for that confusion.

    I tried both Bootstrapper Manifest Generator for 2005 and Bootstrapper Manifest Generator for 2008. And the BMG (Bootstrapper Manifest Generator) for 2005 works well on my machine, when I built the project, it put the bootstrapper package to the package folder(C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\BootStrapper\Packages) automatically. However, When I tried to use BMG for 2008, it put the prerequisite package to the current user's document folder. But when I copied the manifest files as well as package files to the package folder(C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages), it worked well for me.

    Thanks,
    Rong-Chun Zhang

    Please mark the replies as answers if they help and unmark if they don't.
    Friday, November 14, 2008 5:43 AM
  • Hi;

    To confirm, you were able to use the BMG to create a bootstrapper for J# 2.0 second edition? If so, we'll try again. Can you please tell me what registry entries we use to determine if we are installing on a 32-bit, 64-bit, or IA-64 system? And what registry entries we check to see if J# second edition is already installed.

    Also what is the best way to handle the case of an earlier version of J# being installed. If that is the case, you need to exit the new installer and uninstall the old version, then run the new installer. We would like to make that whole process invisible to the user.

    thanks - dave
    Cubicle Wars - http://www.windwardreports.com/film.htm
    Friday, November 14, 2008 4:15 PM

  • Hi Dave,

    Yes, I can use BMG to generate J# 2.0 second edition. To detect if J# 2.0 second edition is installed, the following thread would help.

    http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3078919&SiteID=1

    Thanks,
    Rong-Chun Zhang



    Please mark the replies as answers if they help and unmark if they don't.
    Monday, November 17, 2008 3:10 AM
  • Ok, we'll try it.

    Any suggestions on how to handle the upgrade case where the installer tells you to remove the old version, then re-start the installer?

    How do we, in the bootstrapper, determine is we are 32-bit, 64-bit, or IA-64 and then install the correct version based on that?

    Is it safe to point to the installers at the MS site or should we put them on our server where we know they won't be moved?

    thanks - dave
    Cubicle Wars - http://www.windwardreports.com/film.htm
    • Edited by DavidThi808 Monday, November 17, 2008 4:08 PM
    Monday, November 17, 2008 4:07 PM

  • Hi Dave,

    Not sure the J# 2.0 package will remove the previous version automatically, if it doesn't, you can write you own program to do the stuff like the SQL Express SP 2 does. For more information, please check:

    https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2851359&SiteID=1

    DavidThi808 said:

    How do we, in the bootstrapper, determine is we are 32-bit, 64-bit, or IA-64 and then install the correct version based on that?

    I would like to you create different package for different platform. This is easy to achieve.

    Thanks,
    Rong-Chun Zhang





    Please mark the replies as answers if they help and unmark if they don't.
    Tuesday, November 18, 2008 9:44 AM