.ocx vs dll use in a .asp

[=?Utf-8?B?SkM=?=]

I currently have a .asp on a 2k server that calls calls a .ocx with
parameters that process data and returns info back to the .asp. I have
rewritten the .ocx using VS2005 vb which creates a dll that would replace the
..ocx. Problem is since the dll cannot be registered the asp cannot access it.
What is best way to do this with .net?
or is there a better place to ask this question?

[Scott M.]

You set your .NET project to "Register for COM InterOp', which is in the
project's settings.

This creates a CCW (COM Callable Wrapper) assembly that you can, in fact
register on your server and use in Classic ASP.
"JC" <[e-mail] in message
news:7C**********************************@microsof t.com...

>I currently have a .asp on a 2k server that calls calls a .ocx with
parameters that process data and returns info back to the .asp. I have
rewritten the .ocx using VS2005 vb which creates a dll that would replace
the
.ocx. Problem is since the dll cannot be registered the asp cannot access
it.
What is best way to do this with .net?
or is there a better place to ask this question?