Instantiating The ASP.DLL
Is there a way to do a CreateObject("") on the ASP.DLL?
View Replies
ADVERTISEMENT
Instantiating A Web Service
I have created a web service consisting of 5 different functions. I would like to make the service available in another web project. My first thought is to add a web reference to the webserver (How):
*goto project then add web reference
*Set the url to reflect the path of the web reference
*The add the web reference
My next thought is instantiate the webservice *dim n as new webservicename. This is were I run into problems.
Instantiating Object From Custom ActiveX DLL
I've been provided with a custom ActiveX DLL (written in C++) that reads a certiifcate to generate a signature for a passed XML string, and I'm having trouble instantiating it.
The DLL is registered succesfully on my computer and I've explicitly granted IUSR_<machinename> to use it. Code:
VB.NET Classlibrary Not Instantiating Properly In ASP Pages
Ok, I've been hung up on this issue for quite some time now and I would
like some help in getting it to work. I think this may be a setup issue
but I'd like to ask your eminences first.
Here's some backstory: I need to create a VB.NET classlibrary (or another
structure) to use objects for our business logic. However, as our upgrade
is an ongoing process, I must enable this structure to be run in both ASPX
and ASP pages.
Here's what goes wrong: I create a new solution. Create two projects, one
a ASP.NET web app, the other a classLibrary. I put a basic hello world
object into the classlibrary then get a return string from it in both an
ASP and ASPX page. Yes, the classlibrary has the build option checked to
"register for COM interop."
Now, the ASPX page runs fine - but the ASP page gives me the following
cryptic error:
Error Type:
(0x80070002)
/webApplication1/test1.asp, line 3
Line 3 is the Server.CreateObject command for the object in question.
No error string. The error code, when googled, reveals that it's "file not
found." That's about as useful as a kick in the ass. What am I doing
wrong? Why can't my ASP page use this object? If I can only get this
functional then I will have no further issues - we can start moving our
business logic and data logic from the legacy ASP pages to an object-based
back end.