I converted my asp page to aspx, now Server.CreateObject doesn't work for a registered COM object
that I used before. There is no error message. I just get empty output.

Very simple code:

 dim Obj
 Obj = Server.CreateObject("Test.Application")
 call Obj.MyMethod(StrIn, StrOut)
 Obj = Nothing


How can I fix this?

(ASP.NET v1.1, WinXp Pro IIS v5.1)

Are you using Visual Studio .NET? If so, add a reference to the DLL, and VS will create a wrapper for the COM object. Then in your code, you can instantiate the control like you would any other control.
Don't use Server.CreateObject, but something like this:

Dim Obj As Test.Application
Obj = New Test.Application()

You can also use a tool called TlbImp.exe to convert your type library to a .NET assembly.

Cheers,

Imar



---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

It's a 3rd party component, so no, I can't add anything to the DLL. I tried using TlbImp.exe
on it and it created another DLL, but I don't know what to do with this new DLL. It doesn't
have any export functions, and can't register it either.

Oh, you mean create a wrapper for this DLL and try to use the wrapper instead?

I could probably try to do that, but this 3rd party component is already an ActiveX
component, it works fine with ASP, so I didn't think it would matter with
ASP.NET.

That is correct. The new DLL it creates cannot be registered. It's not a COM DLL, it's a .NET assembly, ready for XCopy deployment.

You'll need to move the new DLL to the Bin folder of your application, so it becomes accessible by your ASP.NET application.

You don't have to add anything to the old DLL. The tool creates a new DLL that acts as a wrapper. That is, you app talks to your new DLL which in turn relays its messages to the old DLL.

Search Google for TlbImp.exe and ASP.NET and you'll find plenty of examples, like: http://www.aspalliance.com/articleVi...aId=377&pId=-1

This may not be the best article, but it was the first I found. There are lots more....

Cheers,

Imar


---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

Thanks for the info. Small detail: where is the 'bin' directory?

When I installed ASP.NET on my computer, it didn't create one.

But it did create some other directories:
C:\Inetpub\wwwroot\aspnet_client
C:\Inetpub\wwwroot\aspnet_client\system_web
C:\Inetpub\wwwroot\aspnet_client\system_web\1_1_43 22

You are supposed to create the bin directory.

Thanks for the one-line answer, but you didn't say where I should create it.

Found it!
Response.Write ("BinDirectory: " & HttpRuntime.BinDirectory & "<BR>")

Usually, the Bin folder is located directly under the application's root.

So, for the default Web site, that would be:

C:\Inetpub\wwwroot\Bin

And for a custom Application you created it could be something like:

C:\Inetpub\wwwroot\MyApplication\Bin

Did you get it to work?

Imar


---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

Great! Got it working. I used your example:

 Dim Obj As Test.Application
 Obj = New Test.Application()

 I believe this header is also necessary:
<% @Import Namespace="test" %>


 I tried using Server.CreateObject, but it gave me errors:

 Dim Obj
 Obj = Server.CreateObject("test.Application")


Server Error in '/' Application.
--------------------------------------------------------------------------------

Could not create an object of type 'test.Application'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: Could not create an object of type 'test.Application'.


I hope the string isn't case sensitive. I tried both cases,
still gives me an error. Doesn't matter, the first way works great.
Thanks.
 :)