using assemblies registered with regsvr32

[Grant Merwitz]

Hi

We have just bought a product what has a classic ASP front end that uses 2
assemblies.
These are registered with the following command:
regsvr32 Repository.dll /s
regsvr32 Dynu.dll /s

The way they are used int the code is as follows:
dim objUser
Set objUser = Server.CreateOb ject("IdentifyR epository.clsUs er")
Now how can i use this in ASP.NET code.
I believe i'll be using the System.Runtime. InteropServices namespace,
but am battling to find good articles to guide me on how, or infact am not
entirely sure what i'm looking for.

Any advice/guidance will be appreciated, or if anyone can point me to a good
article

TIA

Grant

[Jan Peter Stotz]

Grant Merwitz schrieb:

We have just bought a product what has a classic ASP front end that uses 2
assemblies.
These are registered with the following command:
regsvr32 Repository.dll /s
regsvr32 Dynu.dll /s
AFAIK regsvr32 can not work with assemblies. What you got are two
Containter with COM/ActiveX-Objects.
The way they are used int the code is as follows:
dim objUser
Set objUser = Server.CreateOb ject("IdentifyR epository.clsUs er")

That is the late binding variant. This way is not wrong but you should
better create a wrapper-assembly with tlbimp.exe for each dll you have.

See tlbimp documentation:
http://msdn.microsoft.com/library/de...rtlbimpexe.asp

Jan

[Grant Merwitz]

Thanks for your advice

"Jan Peter Stotz" <jp*****@gmx.de > wrote in message
news:t9******** *************** *****@40tude.ne t...

Grant Merwitz schrieb:

We have just bought a product what has a classic ASP front end that uses
2
assemblies.
These are registered with the following command:
regsvr32 Repository.dll /s
regsvr32 Dynu.dll /s

AFAIK regsvr32 can not work with assemblies. What you got are two
Containter with COM/ActiveX-Objects.

The way they are used int the code is as follows:
dim objUser
Set objUser = Server.CreateOb ject("IdentifyR epository.clsUs er")

That is the late binding variant. This way is not wrong but you should
better create a wrapper-assembly with tlbimp.exe for each dll you have.

See tlbimp documentation:
http://msdn.microsoft.com/library/de...rtlbimpexe.asp

Jan