64-bit Installer issue: Wow6432Node entries

Discussion in 'Windows 64bit' started by sl, Jan 2, 2007.

  1. sl

    sl Guest

    Hi All,

    I am working on 64-bit porting of my application which includes a DLL
    and a WIX base installer for installing the DLL and doing Reg Entries.

    I have build 64-bit version of both DLL and Installer but still facing
    an issue.

    When i start my installer, it sends the registry entreis to
    HKCR\Wow6432Node\CLSID instead of
    HKCR\CLSID.

    Now when i manually do entries to HKCR\CLSID, my app works absolutely
    fine.

    While reading on net:
    http://msdn2.microsoft.com/en-us/library/aa367430.aspx
    i got to know that, for making installers as 64-bit apps, we need to
    modify TEMPLATE SUMMARY and specify for each 64-bit component to be
    64-bit using "msidbComponentAttributes64bit bit in the Attributes
    column of the Component Table".

    Now my question is:
    1) If i mark msidbComponentAttributes64bit bit for my components, is it
    ensured that the Registry entries will go to the right place i.e.
    HKCR\CLSID
    2) I am not sure how to use Attribute field of Component Table in Wix.
    Do not know the syntax.
    Is it having the syntax as :
    Win64='yes'

    *** I do not want to use Registry Redirection "KEY_WOW64_32KEY" here.

    Thanks alot.

    Regards,
    Shreshth
     
    sl, Jan 2, 2007
    #1
    1. Advertisements

  2. I am really rusty - could it be an old pre-processor directive that is
    hanging about?

    Tony. . .
     
    Tony Sperling, Jan 2, 2007
    #2
    1. Advertisements

  3. sl

    sl Guest

    Hi Tony,

    Could you please elaborate what you mena to say???

    Regards,
    Shreshth
     
    sl, Jan 3, 2007
    #3
  4. Sorry, I realise this may not be C/C++, I am assuming that anything you are
    doing in the pre-processing stage can jump out and bite you in the leg at a
    much later stage and 'type' definitions are easy to miss in any context.

    This is really not a developer's group - some hang around here, but you
    should have more success putting that question to a developer forum.


    Tony. . .
     
    Tony Sperling, Jan 3, 2007
    #4
  5. Hello Shreshth,
    Let me preface this that I am not a developer, but I asked the question and
    this is what I got back for a response.
    1.> If the component is marked as 64-bit, then MSI writes registry entries
    to the 64-bit hive. So marking the component as 64-bit enables this when
    combined with a package that is marked as 64-bit.


    2.> There are a number of different authoring tools for Windows Installer,
    with Wix being one of them. The documentation on MSDN describes the
    resultant MSI database package entry information. For the specific
    authoring tool, the authoring tool's own documentation should be consulted.
    Wix's documentation is available on sourceforge.net and is included in the
    wix.chm file. Typically win64=yes for the attribute will work, but the
    individual should consult the authoring tool's documentation.

    Thanks,
    Darrell Gorter[MSFT]

    This posting is provided "AS IS" with no warranties, and confers no rights
    --------------------
    |>From: "Tony Sperling" <>
    |>References: <>
    <>
    <>
    |>Subject: Re: 64-bit Installer issue: Wow6432Node entries
    |>Date: Wed, 3 Jan 2007 11:44:49 +0100
    |>Lines: 72
    |>X-Priority: 3
    |>X-MSMail-Priority: Normal
    |>X-Newsreader: Microsoft Outlook Express 6.00.2800.1807
    |>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
    |>X-Antivirus: avast! (VPS 0666-1, 31-12-2006), Outbound message
    |>X-Antivirus-Status: Clean
    |>Message-ID: <>
    |>Newsgroups: microsoft.public.windows.64bit.general
    |>NNTP-Posting-Host: 82.143.202.17
    |>Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
    |>Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.64bit.general:1304
    |>X-Tomcat-NG: microsoft.public.windows.64bit.general
    |>
    |>Sorry, I realise this may not be C/C++, I am assuming that anything you
    are
    |>doing in the pre-processing stage can jump out and bite you in the leg at
    a
    |>much later stage and 'type' definitions are easy to miss in any context.
    |>
    |>This is really not a developer's group - some hang around here, but you
    |>should have more success putting that question to a developer forum.
    |>
    |>
    |>Tony. . .
    |>
    |>
    |>|>> Hi Tony,
    |>>
    |>> Could you please elaborate what you mena to say???
    |>>
    |>> Regards,
    |>> Shreshth
    |>>
    |>>
    |>> Tony Sperling wrote:
    |>> > I am really rusty - could it be an old pre-processor directive that is
    |>> > hanging about?
    |>> >
    |>> > Tony. . .
    |>> >
    |>> >
    |>> > |>> > > Hi All,
    |>> > >
    |>> > > I am working on 64-bit porting of my application which includes a
    DLL
    |>> > > and a WIX base installer for installing the DLL and doing Reg
    Entries.
    |>> > >
    |>> > > I have build 64-bit version of both DLL and Installer but still
    facing
    |>> > > an issue.
    |>> > >
    |>> > > When i start my installer, it sends the registry entreis to
    |>> > > HKCR\Wow6432Node\CLSID instead of
    |>> > > HKCR\CLSID.
    |>> > >
    |>> > > Now when i manually do entries to HKCR\CLSID, my app works
    absolutely
    |>> > > fine.
    |>> > >
    |>> > > While reading on net:
    |>> > > http://msdn2.microsoft.com/en-us/library/aa367430.aspx
    |>> > > i got to know that, for making installers as 64-bit apps, we need to
    |>> > > modify TEMPLATE SUMMARY and specify for each 64-bit component to be
    |>> > > 64-bit using "msidbComponentAttributes64bit bit in the Attributes
    |>> > > column of the Component Table".
    |>> > >
    |>> > > Now my question is:
    |>> > > 1) If i mark msidbComponentAttributes64bit bit for my components, is
    |>it
    |>> > > ensured that the Registry entries will go to the right place i.e.
    |>> > > HKCR\CLSID
    |>> > > 2) I am not sure how to use Attribute field of Component Table in
    Wix.
    |>> > > Do not know the syntax.
    |>> > > Is it having the syntax as :
    |>> > > Win64='yes'
    |>> > >
    |>> > > *** I do not want to use Registry Redirection "KEY_WOW64_32KEY"
    here.
    |>> > >
    |>> > > Thanks alot.
    |>> > >
    |>> > > Regards,
    |>> > > Shreshth
    |>> > >
    |>>
    |>
    |>
    |>
     
    Darrell Gorter[MSFT], Jan 4, 2007
    #5
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.