Calling COM from ASP.NET

[Sid]

Is it possible to call compiled COM components directly
from ASP.NET without having to set a reference to them
using the IDE?

e.g. in ASP you could use Server.CreateObject("somedll")
but for some reason this does not work in ASP.NET, is this
actually possible?

[Cowboy \(Gregory A. Beamer\)]

The reference is necessary, as you have to create the .NET callable wrapper
for the COM component. There is interop involved when you go across the
COM/.NET barrier.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

************************************************** ********************
Think Outside the Box!
************************************************** ********************
"Sid" <an*******@discussions.microsoft.com> wrote in message
news:09****************************@phx.gbl...

Is it possible to call compiled COM components directly
from ASP.NET without having to set a reference to them
using the IDE?

e.g. in ASP you could use Server.CreateObject("somedll")
but for some reason this does not work in ASP.NET, is this
actually possible?

[Sid]

Thanks for replying, can I just clarify, if I am therefore
writing ASP.NET pages using notepad, then I am unable to
call COM components that I have previously created in VB
6.0? Or is it possible to set a reference to a dll
programmatically?

-----Original Message-----
The reference is necessary, as you have to create the .NET callable wrapperfor the COM component. There is interop involved when you go across theCOM/.NET barrier.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

************************************************* ********* ************Think Outside the Box!
************************************************* ********* ************"Sid" <an*******@discussions.microsoft.com> wrote in messagenews:09****************************@phx.gbl...

Is it possible to call compiled COM components directly
from ASP.NET without having to set a reference to them
using the IDE?

e.g. in ASP you could use Server.CreateObject("somedll")
but for some reason this does not work in ASP.NET, is this actually possible?

.

[David Browne]

"Sid" <an*******@discussions.microsoft.com> wrote in message
news:00****************************@phx.gbl...

Thanks for replying, can I just clarify, if I am therefore
writing ASP.NET pages using notepad, then I am unable to
call COM components that I have previously created in VB
6.0? Or is it possible to set a reference to a dll
programmatically?

First off, you don't need an interop assembly.

If you are using VB, at least, you can just use CreateObject and late
binding.

Dim d As Object = CreateObject("MyComponent.MyClass")
d.DoSomething()

This will use late binding to access the component, just like in classic
ASP.

If you want to early-bind to the component, you do need an interop assembly.
But you still don't need VS. You can use tlbimp.exe to generate the interop
assembly, and then add a directive to your aspx page to reference it.

David

[Ingrid]

David you saved my day with this mail, thanks ! :-)
Ingrid

First off, you don't need an interop assembly.

If you are using VB, at least, you can just use CreateObject and late
binding.

Dim d As Object = CreateObject("MyComponent.MyClass")
d.DoSomething()

This will use late binding to access the component, just like in classic
ASP.

If you want to early-bind to the component, you do need an interop assembly. But you still don't need VS. You can use tlbimp.exe to generate the interop assembly, and then add a directive to your aspx page to reference it.

David