we will now use Regasm on managed .NET librarie instead of Regsvr32

Where we once used (might be still using) Regsvr32 on unmanaged COM libraries, we will now use Regasm on managed .NET libraries.

“Regsvr32 (http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/regsvr32.mspx) is the command-line tool that registers .dll files as command components in the registry“

“Regasm.exe, the Assembly Registration tool (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cptools/html/cpgrfassemblyregistrationtoolregasmexe.asp) that comes with the .NET SDK, reads the metadata within an assembly and adds the necessary entries to the registry, which allows COM clients to create .NET Framework classes transparently. Once a class is registered, any COM client can use it as though the class were a COM class. The class is registered only once, when the assembly is installed. Instances of classes within the assembly cannot be created from COM until they are actually registered.“

To register an assembly programmatically, see the RegistrationServices class (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemruntimeinteropservicesregistrationservicesclasstopic.asp) and ComRegisterFunctionAttribute (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemruntimeinteropservicescomregisterfunctionattributeclasstopic.asp)