all groups > dotnet interop > october 2004 >
You're in the

dotnet interop

group:

error msg "assembly identity could not be determined"


Re: error msg "assembly identity could not be determined" Phil Wilson
10/5/2004 8:28:48 AM
dotnet interop:
You haven't got a 1.0.* in your assemblyinfo file have you? that will make
the version different at every build, and therefore different from the one
that is identified in the interop registration entries. See if your
HKCR\CLSID\{class guid} registration entries match your assembly in version,
sn.
--
Phil Wilson
[MVP Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.html?bID=280

[quoted text, click to view]

error msg "assembly identity could not be determined" Rudy
10/5/2004 4:52:48 PM
I created a .NET-DLL and it should be called from a VB6 - program.
I created key.snk file added the path to the assemblyInfo-file, I gave a
GUID to all public classes, I created a tlb and ran gacutil. Also I see it
under windows/assembly! Although when running VB 6 that calls the DLL I get
an error message 'runtime error' 'assembly identity could not be
determined'! Does anyone has any idea what to try next?

Thanx for info

Rudy

Re: error msg "assembly identity could not be determined" Rudy
10/5/2004 6:47:29 PM
Yes, I have, sorry forgot about that! But I haven't got a Version entry in
HKCR/.../CLSID/. Maybe that's the problem?

"Phil Wilson" <pdjwilson@nospam.cox.net> schrieb im Newsbeitrag
news:evrLo%23uqEHA.556@tk2msftngp13.phx.gbl...
[quoted text, click to view]

Re: error msg "assembly identity could not be determined" Luis Abreu
10/5/2004 7:59:40 PM
yes, you should turn the version number into a fixed one. btw, if you
recompile your project, don't forget to add it again to the gac and, if
necessary (I think that it all depends on waht you've changed), register it
again (by using regasm).

--
---
Regards,
Luis Abreu
http://weblogs.pontonetpt.com/luisabreu
http://www.pontonetpt.com

[quoted text, click to view]

Re: error msg "assembly identity could not be determined" Rudy
10/6/2004 2:42:53 PM
Sorry, I meant I forgot to mention that I HAVE got a fixed version number in
my AssemblyInfo! And I do the above steps with every recompiling. But always
the same error in VB6.


"Luis Abreu" <labreu@gmail.com> schrieb im Newsbeitrag
news:e5BZ81wqEHA.1668@TK2MSFTNGP14.phx.gbl...
[quoted text, click to view]

AddThis Social Bookmark Button