RegASM

  • Thread starter Thread starter Chad Z. Hower aka Kudzu
  • Start date Start date
Only if you want an assembly to be registered as an ActiveX DLL, then use
regasm.exe to register it (equivalent of regsvr32.exe in VB6 I would say).
 
Chris Botha said:
Only if you want an assembly to be registered as an ActiveX DLL, then use
regasm.exe to register it (equivalent of regsvr32.exe in VB6 I would say).

Define "registered as an ActiveX DLL".

I know what this means in a non .net context, but Im not sure what
implications it would have regarding .net.

Im just building classes that are exported via assembly. Right now they are
not installed into the vs.net toolbox, but will be at a later date.


--
Chad Z. Hower (a.k.a. Kudzu) - http://www.hower.org/Kudzu/
"Programming is an art form that fights back"


ELKNews - Get your free copy at http://www.atozedsoftware.com
 
I’ve build a dll written in c# with guid and progId attributes given, but failed to register via regasm. What’s wrong with this?!
 
Also known as a COM DLL, thus can be used by a VB6 program, the old ASPs, MS
Access, etc, etc.
If your .net assemblies will only be used in the .net environment, then you
don't register them.
 
Use the /codebase switch when you run regasm

Fatih said:
I've build a dll written in c# with guid and progId attributes given, but
failed to register via regasm. What's wrong with this?!
 
When you want a non-.NET client wants to use a .NET assembly you have to
expose the .NET assembly as a COM Dll. You can do this by registering the
assembly using regasm.exe.
Regasm.exe generates a type library (.tlb) for the .NET assembly which can
be used by Non-.NET client(such as VB 6, ASP) to get the information of the
types defined in the assembly.
I think this clears your doubt.

regards,
Ashish Sheth
 
Back
Top