Deployment - registering assemblies

[CybrWeez]

I've tried using the Register property of a deployment project, it works fine for COM components, but for Assemblies, I've tried vsdraCOM and vsdraCOMRelativePath, neither seems to do anything. No tlb file is generated, and no entry in OleView. I've tried registering through Custom Action, but the problem is in Uninstall, you can't use custom action because the dll's are deleted before any custom action is run which could unregasm. Has anyone dealt w/installing assemblies needing to be regasmed?

[wduros1]

CybrWeez wrote: I've tried vsdraCOM and vsdraCOMRelativePath These two settings only do any magic if the assembly is designed to work through a CCW (Com Callable Wrapper). Basically, if you have designed your assembly to be a COM component. I have used these settings with success. I found a great .NET pdf library that I needed to use in VB6, so I wrote a wrapper object that looked like the VB6 printer object. Using attributes to control the visibility of my properties and methods, then using CCW to expose the object to the COM world. Worked great. :-D In the project properties of your source project (Not the deployment project), check the "Register for COM interop" to get the TBL built, etc. Also, using the various attibutes can make your assembly look much better to those COM eyes... Imports System.Runtime.InteropServices ' Expose this object as a COM object _ Public Class PDFPrinter ' Content Goes Here End Class Then, in the deployment project... [cPDFWriter.tbl] Register=vsdrfCOM [cPDFPrinter.dll] Register=vsdrfCOM