tlbexp

Exposing nested arrays to COM from .NET

I have a method in .NET (C#) which returns string[][]. When using RegAsm or TlbExp (from the .NET 2.0 SDK) to create a COM type library for the containing assembly, I get the following warning: WARNING: There is no marshaling support for nested arrays. This warning results in the method in question not being exported into the gener...

COM Interface question - .NET

Hi Recently I was reading about interop marshalling but I still don't understand one thing. To make .NET assembly visible to COM I need to use tlbexp tool and/or regasm tool. To make COM visible to .NET assebly I have to use tlbimp tool - all that is clear for me. Apart from that, I've seen on the internet a lot of code dealing with C...

Looking for suggestions on how to troubleshoot tlbexp exception

We have a .Net assembly that is exported to COM. I made changes to an assembly that assembly uses and now tlbexp fails with a stack overflow exception. I assume that it is a result of one of the changes that I made, but I am unsure how to figure out which change is to blame. Is there a method that someone knows of to capture the type ...

How to Register a Type Library without RegAsm.exe

I want to know if it's possible to register a type library without using the RegAsm tool. Here is my situation, which will hopefully explain why I want to do this: I'm developing an assembly in .NET that will provide some modern functionality for our older VB6 applications. I have successfully registered the assembly and the type libr...

problem bex error

Problem signature: Problem Event Name: BEX Application Name: iexplore.exe Application Version: 8.0.6001.18882 Application Timestamp: 4b3ed243 Fault Module Name: msjava.dll Fault Module Version: 5.0.2752.0 Fault Module Timestamp: 35747274 Exception Offset: 000c5a6c Exception Code: c0000005 Exception Data: 00000008 OS...

tlbexp.exe changes method names' case

I have a rather strange problem. I am exporting an interface from a C# library to COM. I have enabled the 'register with COM' project setting, so it calls tlbexp.exe to make the type libs. We use camel case on our method names and I noticed that the exported type library changes these any method that happens to coincide with a class nam...