Register in GAC - vsdrpCOM

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Gene Vangampelaere - 04 Nov 2004 09:22 GMT

Hi,

I'm having a strange problem and I'm not able to resolve it. Can someone
help me please ?

I want to create a MSI (setup package) to install a assembly into the GAC.
When I build the project I get this error:

Unable to build assembly named 'NameOfTheAssembly.dll', HRESULT ==
'8007065B'

The register property of the primary output is set to vsdrpCOM.
When I set it to vsdrpDoNotRegister then I can build the setup package but
... the assembly is not registered of course !

Reply to this Message

Phil Wilson - 04 Nov 2004 16:28 GMT

What happens if you don't use the Project Output choice? Just add the
assembly by browsing to it, then setting registration to vsdraCOM. (lower
case 'a' for assembly, lower case 'p' for project output).

Signature

Phil Wilson
[Microsoft MVP-Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.html?bID=280

> Hi,
>
[quoted text clipped - 10 lines]
> When I set it to vsdrpDoNotRegister then I can build the setup package but
> ... the assembly is not registered of course !

Reply to this Message

Gene Vangampelaere - 09 Nov 2004 07:29 GMT

I think I found the solution:
I used the project output into 2 directories (GAC and Application dir) and I
let it registering as COM twice. Now I only registered it in the GAC and it
works!

There where also a lot registry entries in my registry (I tested the dll a
lot!). I deleted them all and compiled again. Maybe that was also a problem
... who knows ... ;-)

Thanks for the reply anyway !!

G.

> What happens if you don't use the Project Output choice? Just add the
> assembly by browsing to it, then setting registration to vsdraCOM. (lower
[quoted text clipped - 13 lines]
> > When I set it to vsdrpDoNotRegister then I can build the setup package but
> > ... the assembly is not registered of course !

Reply to this Message

Phil Wilson - 09 Nov 2004 15:25 GMT

If you have a lot of registry entries for the class, it might be because you
haven't specified an explicit Guid for the class and Visual Studio is
generating a new one every time you change something and rebuild. It helps
to nail down the version too instead of an AssemblyVersion of 1.0.*.

Signature

Phil Wilson
[Microsoft MVP-Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.html?bID=280

>I think I found the solution:
> I used the project output into 2 directories (GAC and Application dir) and
[quoted text clipped - 34 lines]
> but
>> > ... the assembly is not registered of course !

Reply to this Message

Carlos Cortes - 11 Nov 2004 01:49 GMT

This blog also covers this problem:
http://blogs.msdn.com/omars/archive/2004/04/28/122321.aspx

Reply to this Message

anil - 24 Nov 2004 20:23 GMT

Hey Phil,

I tried removing the primary output and adding just the assembly. I haven't
specified any GUIDs in the code. My installation package keeps failing with
this error. I also followed all the steps in the blog. But no luck. Can u
suggest anything ?

-Anil

> If you have a lot of registry entries for the class, it might be because
> you haven't specified an explicit Guid for the class and Visual Studio is
[quoted text clipped - 40 lines]
>> but
>>> > ... the assembly is not registered of course !

Reply to this Message

Rate this thread:

Register in GAC - vsdrpCOM

Free Magazines