Type library exporter error - Urgent help needed
-
Hi every one, Am unable to resolve this error: Error: The assembly "D:\ActiveXProjects\csharpactivexglobe\csharpactivexglobe\bin\Debug\csharpactivexglobe.dll" could not be converted to a type library. Type library exporter encountered an error while processing'csharpactivexglobe.Globe.ActiveXObject, csharpactivexglobe'. Error: Element not found. csharpactivexglobe I was trying to do regasm /codebase /tlb MyAssemblie.dll but unable to convert to a type library. Could you please give me any suggession to fix this error. Thanking you all in advance, Cheers & Regards, Sharat. :)
sharat
-
Hi every one, Am unable to resolve this error: Error: The assembly "D:\ActiveXProjects\csharpactivexglobe\csharpactivexglobe\bin\Debug\csharpactivexglobe.dll" could not be converted to a type library. Type library exporter encountered an error while processing'csharpactivexglobe.Globe.ActiveXObject, csharpactivexglobe'. Error: Element not found. csharpactivexglobe I was trying to do regasm /codebase /tlb MyAssemblie.dll but unable to convert to a type library. Could you please give me any suggession to fix this error. Thanking you all in advance, Cheers & Regards, Sharat. :)
sharat
First of all, C# cannot target building an ActiveX component. It can make something that looks and acts like one, but isn't a true ActiveX. Which brings me to the question. Is this component attributed to be exposed to COM?
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008 -
Hi every one, Am unable to resolve this error: Error: The assembly "D:\ActiveXProjects\csharpactivexglobe\csharpactivexglobe\bin\Debug\csharpactivexglobe.dll" could not be converted to a type library. Type library exporter encountered an error while processing'csharpactivexglobe.Globe.ActiveXObject, csharpactivexglobe'. Error: Element not found. csharpactivexglobe I was trying to do regasm /codebase /tlb MyAssemblie.dll but unable to convert to a type library. Could you please give me any suggession to fix this error. Thanking you all in advance, Cheers & Regards, Sharat. :)
sharat
I have had the same problem sice yesterday, I was spending today to find out waht the problem is. Beside some solutions I hvae found (duplicate guid for assembly and class) but did not work for me, I found the solution for me: I am using a vb6 com-class library dll as a reference in my .NET project. I have changed that com class library dll by removing a function from one of the classes, because it is no more used/needed. After adding this function and recompiling the vb6 com library, registering again in .NET project, the problem was gone. It seams, that the type library exporter remebers some information somewhere, that even a clean did not swipe out. My be the old version of the type library was still hanging aaround somewhere in the registry. Afterwards I again removed the unnecessary function from the dll, unregistered to old one registered the new one and, even then the problem was gone. So seams to be a windows registry mystery. I hope it helps some folks, so they do not search and loose hours and hours like i did. Wolfiko
-
I have had the same problem sice yesterday, I was spending today to find out waht the problem is. Beside some solutions I hvae found (duplicate guid for assembly and class) but did not work for me, I found the solution for me: I am using a vb6 com-class library dll as a reference in my .NET project. I have changed that com class library dll by removing a function from one of the classes, because it is no more used/needed. After adding this function and recompiling the vb6 com library, registering again in .NET project, the problem was gone. It seams, that the type library exporter remebers some information somewhere, that even a clean did not swipe out. My be the old version of the type library was still hanging aaround somewhere in the registry. Afterwards I again removed the unnecessary function from the dll, unregistered to old one registered the new one and, even then the problem was gone. So seams to be a windows registry mystery. I hope it helps some folks, so they do not search and loose hours and hours like i did. Wolfiko
Wow Thanks... I will try this and see if it is my issue.
You can only be young once. But you can always be immature. - Dave Barry