|
|
You're in the
visual studio .net general
group:Deploying assembly for COM interop
visual studio .net general:
It looks like you're doing the right thing with the setup project. How do you
know it's not registered properly? Can you see incorrect registry entries? Are you getting an HRESULT you can report? -- Phil Wilson [MVP Windows Installer] ---- [quoted text, click to view] "David-L. Nadeau" <d_l_n@hotmail.com> wrote in message news:eM1hY%230FEHA.3132@TK2MSFTNGP12.phx.gbl... > Hi! > > I have build a setup project in VS 2003. I've setup my project to register > my assembly for COM. Interop. In my setup project I set register to > vsdrpCOM. Unfortunately, when i deploy my application the dll is not > register correctly in the registry. I have to regsiter it manually by doing > regasm "MyDll.dll" /codebase in order to make it visible as a COM object. > > What am I doing wrong ? > > How can I register and unregister my assembly as a COM object automaticly at > deployment ? > > Thanks, > > David > >
Hi!
I have build a setup project in VS 2003. I've setup my project to register my assembly for COM. Interop. In my setup project I set register to vsdrpCOM. Unfortunately, when i deploy my application the dll is not register correctly in the registry. I have to regsiter it manually by doing regasm "MyDll.dll" /codebase in order to make it visible as a COM object. What am I doing wrong ? How can I register and unregister my assembly as a COM object automaticly at deployment ? Thanks, David
I know it is not register properly for two reasons:
1) If i go to DOS and I do Regasm "MyDll" -u the unregistration fail (Subkey does not exist). 2) I know that the registration failed at setup because my assembly is used by a GIS software called ArcMap. When I register my assembly with regasm /codebase I can execute my functions in the GIS. If I simply run the Setup program the functions are not available. I may have found something. When I go to the DOS prompt to call Regasm /codebase the registration succeed, my functions runs in the GIS and they works fine. But, I build an exe to register my dll automatically (see code below) and the registration failed. The error is "File or assembly name ADependentDLL, or one of its dependencies, was not found." I don't know why I get this error because like I said it works with Regasm ? So, probably my setup doesn't register my dll correctly because of the same error and no errors are returned ? Why do I get this error with System.Runtime.InteropServices.RegistrationServices and not Regasm.exe ??? Try Path As String = "C:\Program Files\MyApp\Inventaire.dll" 'This path is ok 100% sure. Dim InstallingAssembly As System.Reflection.Assembly InstallingAssembly = System.Reflection.Assembly.LoadFile(Path) 'This line runs ok i put a msgbox that returns the Fullname of the assembly. Dim Outil As New System.Runtime.InteropServices.RegistrationServices Outil.RegisterAssembly(InstallingAssembly, Runtime.InteropServices.AssemblyRegistrationFlags.SetCodeBase) 'This line failed. Catch MsgBox(Err.Description) End Try Thanks, David "Phil Wilson" <phil.wilson@unisys.spamcom> a écrit dans le message de news:%2395Anm1FEHA.3324@TK2MSFTNGP09.phx.gbl... [quoted text, click to view] > It looks like you're doing the right thing with the setup project. How do you > know it's not registered properly? Can you see incorrect registry entries? Are > you getting an HRESULT you can report? > -- > Phil Wilson [MVP Windows Installer] > ---- > "David-L. Nadeau" <d_l_n@hotmail.com> wrote in message > news:eM1hY%230FEHA.3132@TK2MSFTNGP12.phx.gbl... > > Hi! > > > > I have build a setup project in VS 2003. I've setup my project to register > > my assembly for COM. Interop. In my setup project I set register to > > vsdrpCOM. Unfortunately, when i deploy my application the dll is not > > register correctly in the registry. I have to regsiter it manually by doing > > regasm "MyDll.dll" /codebase in order to make it visible as a COM object. > > > > What am I doing wrong ? > > > > How can I register and unregister my assembly as a COM object automaticly at > > deployment ? > > > > Thanks, > > > > David > > > > > >
There is a known bug (in both VS 2002 and VS 2003) where Regasm fails to
register properly if you are trying to register an assembly and the dependency can't be found. If you run RegAsm in the bin dir, usually the dependencies are copied locally. However, setup projects run regasm from the obj dir (for other important reasons), where the dependency is not available. In this case, setup projects will fail to register correctly. The workaround is to add the assembly to your project as a "file", right click in the File System Editor, and select Add File, and navigate to the assembly in the bin dir. Usually that gets regasm to work and we get the proper registration information. --- David Guyer - VBQA Deployment Testing This posting is provided "AS IS" with no warranties, and confers no rights. -------------------- [quoted text, click to view] >From: "David-L. Nadeau" <d_l_n@hotmail.com> cpmsftngxa06.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12>References: <eM1hY#0FEHA.3132@TK2MSFTNGP12.phx.gbl> <#95Anm1FEHA.3324@TK2MSFTNGP09.phx.gbl> >Subject: Re: Deploying assembly for COM interop >Date: Wed, 31 Mar 2004 15:39:52 -0500 >Lines: 85 >X-Priority: 3 >X-MSMail-Priority: Normal >X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 >Message-ID: <#XXpXB2FEHA.3288@TK2MSFTNGP12.phx.gbl> >Newsgroups: microsoft.public.vsnet.general >NNTP-Posting-Host: eth36.mrn.gouv.qc.ca 142.213.192.36 >Path: .phx.gbl [quoted text, click to view] >Xref: cpmsftngxa06.phx.gbl microsoft.public.vsnet.general:17917
>X-Tomcat-NG: microsoft.public.vsnet.general > >I know it is not register properly for two reasons: > >1) If i go to DOS and I do Regasm "MyDll" -u the unregistration fail (Subkey >does not exist). > >2) I know that the registration failed at setup because my assembly is used >by a GIS software called ArcMap. When I register my assembly with regasm >/codebase I can execute my functions in the GIS. If I simply run the Setup >program the functions are not available. > >I may have found something. When I go to the DOS prompt to call Regasm >/codebase the registration succeed, my functions runs in the GIS and they >works fine. But, I build an exe to register my dll automatically (see code >below) and the registration failed. The error is "File or assembly name >ADependentDLL, or one of its dependencies, was not found." I don't know why >I get this error because like I said it works with Regasm ? > >So, probably my setup doesn't register my dll correctly because of the same >error and no errors are returned ? Why do I get this error with >System.Runtime.InteropServices.RegistrationServices and not Regasm.exe ??? > >Try > > Path As String = "C:\Program Files\MyApp\Inventaire.dll" 'This path is >ok 100% sure. > Dim InstallingAssembly As System.Reflection.Assembly > > InstallingAssembly = System.Reflection.Assembly.LoadFile(Path) 'This >line runs ok i put a msgbox that returns the Fullname of the assembly. > > Dim Outil As New System.Runtime.InteropServices.RegistrationServices > > Outil.RegisterAssembly(InstallingAssembly, >Runtime.InteropServices.AssemblyRegistrationFlags.SetCodeBase) 'This line >failed. > >Catch > > MsgBox(Err.Description) > >End Try > >Thanks, > >David > > >"Phil Wilson" <phil.wilson@unisys.spamcom> a écrit dans le message de >news:%2395Anm1FEHA.3324@TK2MSFTNGP09.phx.gbl... >> It looks like you're doing the right thing with the setup project. How do >you >> know it's not registered properly? Can you see incorrect registry entries? >Are >> you getting an HRESULT you can report? >> -- >> Phil Wilson [MVP Windows Installer] >> ---- >> "David-L. Nadeau" <d_l_n@hotmail.com> wrote in message >> news:eM1hY%230FEHA.3132@TK2MSFTNGP12.phx.gbl... >> > Hi! >> > >> > I have build a setup project in VS 2003. I've setup my project to >register >> > my assembly for COM. Interop. In my setup project I set register to >> > vsdrpCOM. Unfortunately, when i deploy my application the dll is not >> > register correctly in the registry. I have to regsiter it manually by >doing >> > regasm "MyDll.dll" /codebase in order to make it visible as a COM >object. >> > >> > What am I doing wrong ? >> > >> > How can I register and unregister my assembly as a COM object >automaticly at >> > deployment ? >> > >> > Thanks, >> > >> > David >> > >> > >> >> > > >
It works!!!
I was having the same problem. Thanks Antonio --- Posted using Wimdows.net NntpNews Component -
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
| home · blog · groups | Questions? Comments? Contact the dn |