Vista Deployment includes Registering COM component

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

    Vista Deployment includes Registering COM component

    Using Visual Studio 2005 I have VB project that produces a program that is
    to be deployed using a VS2005 deployment project. There are some legacy COM
    components that need to be registered with Windows.

    Everything works jus fine under XP, including the COM components
    self-registration. But when the deployment msi or setup.exe are run under
    Vista (Business Ed), the self-registration fails with an Authorities error -
    even when I hae the UAC turned off.

    I can manually register the COM component after the installation fails, but
    that's not a very elegant way to introduce a new user to the product -
    having the installation fail and requiring them to perform as separate
    manual step.

    Is there any way to get a VS2005 deployment project to register a COM
    component when run under Vista?

    Thanks in advance,
    Geoff

    --

    Geoff Blood - "The ACT! Customizer"
    ACT! Certified Consultant

    Serving the ACC Community since 1994

    The New Hampton Group, Mountain View, CA

    ACT! customized for your success

    geoff@tnhg.com


    AIM: ACTCustomizer



  • Mr. Arnold

    #2
    Re: Vista Deployment includes Registering COM component


    "Geoff Blood" <geoff@tnhg.com wrote in message
    news:%234wRlACc IHA.5160@TK2MSF TNGP05.phx.gbl. ..
    >
    Is there any way to get a VS2005 deployment project to register a COM
    component when run under Vista?
    >
    I would think that the deployment project comes out as an exe, msi ect ect,
    since I have never created a setup project.

    Have you tries right-clicking it and run it with Run As Administrator?

    Comment

    • kimiraikkonen

      #3
      Re: Vista Deployment includes Registering COM component

      On Feb 16, 12:14 am, "Geoff Blood" <ge...@tnhg.com wrote:
      Using Visual Studio 2005 I have VB project that produces a program that is
      to be deployed using a VS2005 deployment project. There are some legacy COM
      components that need to be registered with Windows.
      >
      Everything works jus fine under XP, including the COM components
      self-registration. But when the deployment msi or setup.exe are run under
      Vista (Business Ed), the self-registration fails with an Authorities error -
      even when I hae the UAC turned off.
      >
      I can manually register the COM component after the installation fails, but
      that's not a very elegant way to introduce a new user to the product -
      having the installation fail and requiring them to perform as separate
      manual step.
      >
      Is there any way to get a VS2005 deployment project to register a COM
      component when run under Vista?
      >
      Thanks in advance,
      Geoff
      >
      --
      >
      Geoff Blood - "The ACT! Customizer"
      ACT! Certified Consultant
      >
      Serving the ACC Community since 1994
      >
      The New Hampton Group, Mountain View, CA
      >
      ACT! customized for your success
      >
      ge...@tnhg.comw ww.tnhg.comwww. ACTCustomizer.c om
      AIM: ACTCustomizer
      Is the behaivour same on all target machines? It's possible that not
      be admin or restricted group policy settings may have been causing
      this.

      Comment

      • Geoff Blood

        #4
        Re: Vista Deployment includes Registering COM component

        yes, with the same results. Any other ideas?

        --

        Geoff Blood - "The ACT! Customizer"
        ACT! Certified Consultant

        Serving the ACC Community since 1994

        The New Hampton Group, Mountain View, CA

        ACT! customized for your success

        geoff@tnhg.com


        AIM: ACTCustomizer


        "Mr. Arnold" <MR. Arnold@Arnold.c omwrote in message
        news:%237%23uyU CcIHA.1208@TK2M SFTNGP03.phx.gb l...
        >
        "Geoff Blood" <geoff@tnhg.com wrote in message
        news:%234wRlACc IHA.5160@TK2MSF TNGP05.phx.gbl. ..
        >>
        >Is there any way to get a VS2005 deployment project to register a COM
        >component when run under Vista?
        >>
        >
        I would think that the deployment project comes out as an exe, msi ect
        ect, since I have never created a setup project.
        >
        Have you tries right-clicking it and run it with Run As Administrator?

        Comment

        • Geoff Blood

          #5
          Re: Vista Deployment includes Registering COM component

          It happens on all the machines that I tried. I WAS admin on all machines.
          I'm not familiar with Group policies - what are they, how are they managed,
          andhow could they affect my users when they try to install my program?

          TIA,
          Geoff

          "kimiraikko nen" <kimiraikkonen8 5@gmail.comwrot e in message
          news:60fedd8f-f1a1-433f-9fd0-26887f7f19a2@n5 8g2000hsf.googl egroups.com...
          On Feb 16, 12:14 am, "Geoff Blood" <ge...@tnhg.com wrote:
          >Using Visual Studio 2005 I have VB project that produces a program that
          >is
          >to be deployed using a VS2005 deployment project. There are some legacy
          >COM
          >components that need to be registered with Windows.
          >>
          >Everything works jus fine under XP, including the COM components
          >self-registration. But when the deployment msi or setup.exe are run
          >under
          >Vista (Business Ed), the self-registration fails with an Authorities
          >error -
          >even when I hae the UAC turned off.
          >>
          >I can manually register the COM component after the installation fails,
          >but
          >that's not a very elegant way to introduce a new user to the product -
          >having the installation fail and requiring them to perform as separate
          >manual step.
          >>
          >Is there any way to get a VS2005 deployment project to register a COM
          >component when run under Vista?
          >>
          >Thanks in advance,
          >Geoff
          >>
          >--
          >>
          >Geoff Blood - "The ACT! Customizer"
          >ACT! Certified Consultant
          >>
          >Serving the ACC Community since 1994
          >>
          >The New Hampton Group, Mountain View, CA
          >>
          >ACT! customized for your success
          >>
          >ge...@tnhg.com www.tnhg.comwww .ACTCustomizer. com
          >AIM: ACTCustomizer
          >
          Is the behaivour same on all target machines? It's possible that not
          be admin or restricted group policy settings may have been causing
          this.

          Comment

          • Mr. Arnold

            #6
            Re: Vista Deployment includes Registering COM component


            "Mr. Arnold" <MR. Arnold@Arnold.c omwrote in message
            news:%237%23uyU CcIHA.1208@TK2M SFTNGP03.phx.gb l...
            >
            "Geoff Blood" <geoff@tnhg.com wrote in message
            news:%234wRlACc IHA.5160@TK2MSF TNGP05.phx.gbl. ..
            >>
            >Is there any way to get a VS2005 deployment project to register a COM
            >component when run under Vista?
            >>
            >
            I would think that the deployment project comes out as an exe, msi ect
            ect, since I have never created a setup project.
            >
            Have you tries right-clicking it and run it with Run As Administrator?
            This is what I would do at the moment for a quick workaround. I think Vista
            can still run a Batch file. I would create a Batch file that is using
            Regsvr32 Dllname.dll and register the DLL with the user executing that
            Batch file. You can have the Batch file and the DLL in a zip file, and have
            them unzip it and have them do it, until you figure out to do it with a Net
            deployment project.

            You may have to look at the .Net Framework Configuration polices, off of
            Control Panel/Admin Tools at the machine in question to see what are the
            rights for a .Net solution to do anything at the workstation level. It's a
            shot and also policies on the Vista machine when using the secpol.mmc at the
            Run Box, using Run As Admin rights.




            Comment

            Working...