Re: COM Callable Library Problem
Daniel Petersson <[email protected]>
| Newsgroups | gmane.comp.windows.devel.dotnet.clr |
|---|---|
| Message-ID | <E8FBCCA96548DD46A1AC748F17EEAD9C0E96F6F4E8@cefalo-mail01.cefalo.local> |
if pdGen isn't null then it quite likely that some internal code in your PdfGenerator fails. attach a debugger and set it to "break on throw" exceptions. ( or simply check the StackTrace of the thrown exception ) regards, Daniel ________________________________________ From: Discussion of development on the .NET platform using any managed language [[email protected]] On Behalf Of Brady Kelly [[email protected]] Sent: Monday, January 28, 2008 4:01 PM To: [email protected] Subject: [DOTNET-CLR] COM Callable Library Problem I've just created a COM Callable C# class library, registered with the Register for COM Interop option, just for testing. Then I'm using some VBA code to instantiate the object and call it's only method. When I run the code below, I get an "Object reference not set to an instance of an object." error, but my object isn't Nothing. I suspect the interop to be the problem. Has anyone encountered anything like this before? Set pdGen = New PdfGenerator.PdfGenerator <My C# class> ret = pdGen.GeneratePdf(xmlPath, conn) =================================== This list is hosted by DevelopMentor? http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com