Vista Deployment includes Registering COM component

[Geoff Blood]

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.com
www.ACTCustomizer.com
AIM: ACTCustomizer

[Mr. Arnold]

"Geoff Blood" <ge***@tnhg.comwrote in message
news:%2****************@TK2MSFTNGP05.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?

[kimiraikkonen]

On Feb 16, 12:14 am, "Geoff Blood" <[e-mail]:

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

[e-mail]
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.

[Geoff Blood]

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

ge***@tnhg.com
www.tnhg.com
www.ACTCustomizer.com
AIM: ACTCustomizer
"Mr. Arnold" <MR. Ar****@Arnold.comwrote in message
news:%2******************@TK2MSFTNGP03.phx.gbl...

>
"Geoff Blood" <ge***@tnhg.comwrote in message
news:%2****************@TK2MSFTNGP05.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?

[Geoff Blood]

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

"kimiraikkonen" <ki*************@gmail.comwrote in message
news:60**********************************@n58g2000 hsf.googlegroups.com...

On Feb 16, 12:14 am, "Geoff Blood" <[e-mail]:

>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

[e-mail]
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.

[Mr. Arnold]

"Mr. Arnold" <MR. Ar****@Arnold.comwrote in message
news:%2******************@TK2MSFTNGP03.phx.gbl...

>
"Geoff Blood" <ge***@tnhg.comwrote in message
news:%2****************@TK2MSFTNGP05.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.