Install VB2005 app on 2003 64 bit server

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • TexasAggie96

    #1

    Install VB2005 app on 2003 64 bit server

    I have written a windows service in VS 2005 and created a setup for
    install on a 2003 64 bit server. When the installer adds the registry
    components they are created in the WOW6432NODE key under
    HKEY_LOCAL_MACH INE\SOFTWARE but when the application trys to read the
    registry it looks in the 64 bit section of the registry for the
    registry entries.

    I have created the entries in the 64 bit side and the application works
    just fine.

    What am I doing wrong here? I thought that since this is 32 bit
    application that the installer and application would look at 32 bit
    section.

    Thanks

    James

  • aaron.kempf@gmail.com

    #2
    Re: Install VB2005 app on 2003 64 bit server

    http://www.eweek.com/article2/0,1895,2065392,00.asp

    According to Evans Data's Fall 2006 North American Development Survey,
    overall, developer use of the Visual Basic family has dropped off by 35
    percent since last spring.

    Moreover, Evans said, "As expected, developers are finally leaving VB6
    and earlier versions; they're also leaving VB.NET; which is down by 26
    percent. This means Java now holds the market penetration lead at 45
    percent, followed by C/C++ at 40 percent, and C# at 32 percent."





    TexasAggie96 wrote:
    I have written a windows service in VS 2005 and created a setup for
    install on a 2003 64 bit server. When the installer adds the registry
    components they are created in the WOW6432NODE key under
    HKEY_LOCAL_MACH INE\SOFTWARE but when the application trys to read the
    registry it looks in the 64 bit section of the registry for the
    registry entries.
    >
    I have created the entries in the 64 bit side and the application works
    just fine.
    >
    What am I doing wrong here? I thought that since this is 32 bit
    application that the installer and application would look at 32 bit
    section.
    >
    Thanks
    >
    James

    Comment

    • TexasAggie96

      #3
      Re: Install VB2005 app on 2003 64 bit server

      WTF... This does not answer my question. I am not going to rewrite it
      in java I just want to know why my program is going for the 64 bit side
      of town when reading the regisry and the install is putting all of my
      registry variables into the 32 bit side: HKEY_LOCAL_MACH INE\SOFTWARE
      \WOW6432NODE.

      aaron.kempf@gma il.com wrote:
      http://www.eweek.com/article2/0,1895,2065392,00.asp
      >
      According to Evans Data's Fall 2006 North American Development Survey,
      overall, developer use of the Visual Basic family has dropped off by 35
      percent since last spring.
      >
      Moreover, Evans said, "As expected, developers are finally leaving VB6
      and earlier versions; they're also leaving VB.NET; which is down by 26
      percent. This means Java now holds the market penetration lead at 45
      percent, followed by C/C++ at 40 percent, and C# at 32 percent."
      >
      >
      >
      >
      >
      TexasAggie96 wrote:
      I have written a windows service in VS 2005 and created a setup for
      install on a 2003 64 bit server. When the installer adds the registry
      components they are created in the WOW6432NODE key under
      HKEY_LOCAL_MACH INE\SOFTWARE but when the application trys to read the
      registry it looks in the 64 bit section of the registry for the
      registry entries.

      I have created the entries in the 64 bit side and the application works
      just fine.

      What am I doing wrong here? I thought that since this is 32 bit
      application that the installer and application would look at 32 bit
      section.

      Thanks

      James

      Comment

      • RobinS

        #4
        Re: Install VB2005 app on 2003 64 bit server

        Just ignore that guy; he's trying to annoy people into moving to C#,
        or annoy Microsoft into throwing out VB.Net and going back to VB6,
        which is more likely than anybody in the United States government
        (or any other government, for that matter) admitting they made
        a mistake.

        I don't know the answer to your question, I just wanted you to
        know what the deal was with his response.

        Robin S.
        (Texas A&M graduate too!)
        ------------------------------------
        "TexasAggie 96" <jrwallace96@ms n.comwrote in message
        news:1165297648 .564059.324570@ 73g2000cwn.goog legroups.com...
        WTF... This does not answer my question. I am not going to rewrite it
        in java I just want to know why my program is going for the 64 bit side
        of town when reading the regisry and the install is putting all of my
        registry variables into the 32 bit side: HKEY_LOCAL_MACH INE\SOFTWARE
        \WOW6432NODE.
        >
        aaron.kempf@gma il.com wrote:
        >http://www.eweek.com/article2/0,1895,2065392,00.asp
        >>
        >According to Evans Data's Fall 2006 North American Development Survey,
        >overall, developer use of the Visual Basic family has dropped off by 35
        >percent since last spring.
        >>
        >Moreover, Evans said, "As expected, developers are finally leaving VB6
        >and earlier versions; they're also leaving VB.NET; which is down by 26
        >percent. This means Java now holds the market penetration lead at 45
        >percent, followed by C/C++ at 40 percent, and C# at 32 percent."
        >>
        >>
        >>
        >>
        >>
        >TexasAggie96 wrote:
        I have written a windows service in VS 2005 and created a setup for
        install on a 2003 64 bit server. When the installer adds the registry
        components they are created in the WOW6432NODE key under
        HKEY_LOCAL_MACH INE\SOFTWARE but when the application trys to read the
        registry it looks in the 64 bit section of the registry for the
        registry entries.
        >
        I have created the entries in the 64 bit side and the application works
        just fine.
        >
        What am I doing wrong here? I thought that since this is 32 bit
        application that the installer and application would look at 32 bit
        section.
        >
        Thanks
        >
        James
        >

        Comment

        Working...