wcn2k
12-14-2006, 09:07 AM
Dear dASP community,
I could really use your help and appreciate your assistance in advance.
I am working on a website located at www.gemsafeplastics.com (http://www.gemsafeplastics.com) that is implemented using classic ASP. The page extensions are .html, but don't let that confuse you. The dASP server is set up to run all .html pages through the asp DLL.
Here's my problem:
I need to connect to my PayPal Merchant account for credit card processing through the IBiz PayPal Integrator from /n Software that is available on dASP's server. So far, so good. However, I discovered that dASP only supports the ASP.NET version of this control and not the classic ASP COM object that I need. It was suggested to me that I create a couple ASP.NET pages within my site to just process the credit card transaction and then switch back to classic ASP for the rest of the site's operation. This sounded good to me, so I did a little research and other than having to save a few Session variables in my database so that I can share them between ASP.NET and classic ASP, this solution sounded doable.
This is where my ignorance of ASP.NET comes in. I loaded a couple demo pages available from /n Software for using their object in ASP.NET. I have set up a couple html pages to show you the source code of the main page and the code behind page. They are located here:
www.gemsafeplastics.com/Test/directpayment.html (http://www.gemsafeplastics.com/Test/directpayment.html)
www.gemsafeplastics.com/Test/directpaymentcodebehind.html (http://www.gemsafeplastics.com/Test/directpaymentcodebehind.html)
The actual live page is located here:
www.gemsafeplastics.com/Test/directpayment.aspx (http://www.gemsafeplastics.com/Test/directpayment.aspx)
The problem I'm having is that the code behind page does not appear to get compiled or activated when the submit button is clicked.
Here is some other information:
The /n Software demo directory also includes a web.config file that if I include it in the directory with the directpayment.aspx file, dASP's server will choke on it and generate an error.
I'm hoping that one of you ASP.NET jocks might take a look at what I've done and tell me that I've got my head up my butt and the solution is simple. I'll take my lumps if some of the bleariness in my eyes will go away. /emoticons/smile.gif
Questions:
1) Is there any reason why classic ASP and ASP.NET pages cannot run side by side?
2) Does dASP need to specially configure my account to allow this? Does some kind of virtual directory need to be set up?
3) Any ideas on why my code behind page appears to be ignored?
Again, thank you for your time. Though I'm new to this forum, I promise to come back and contribute. I'm not all take and no give. /emoticons/smile.gif
Kind regards,
David
I could really use your help and appreciate your assistance in advance.
I am working on a website located at www.gemsafeplastics.com (http://www.gemsafeplastics.com) that is implemented using classic ASP. The page extensions are .html, but don't let that confuse you. The dASP server is set up to run all .html pages through the asp DLL.
Here's my problem:
I need to connect to my PayPal Merchant account for credit card processing through the IBiz PayPal Integrator from /n Software that is available on dASP's server. So far, so good. However, I discovered that dASP only supports the ASP.NET version of this control and not the classic ASP COM object that I need. It was suggested to me that I create a couple ASP.NET pages within my site to just process the credit card transaction and then switch back to classic ASP for the rest of the site's operation. This sounded good to me, so I did a little research and other than having to save a few Session variables in my database so that I can share them between ASP.NET and classic ASP, this solution sounded doable.
This is where my ignorance of ASP.NET comes in. I loaded a couple demo pages available from /n Software for using their object in ASP.NET. I have set up a couple html pages to show you the source code of the main page and the code behind page. They are located here:
www.gemsafeplastics.com/Test/directpayment.html (http://www.gemsafeplastics.com/Test/directpayment.html)
www.gemsafeplastics.com/Test/directpaymentcodebehind.html (http://www.gemsafeplastics.com/Test/directpaymentcodebehind.html)
The actual live page is located here:
www.gemsafeplastics.com/Test/directpayment.aspx (http://www.gemsafeplastics.com/Test/directpayment.aspx)
The problem I'm having is that the code behind page does not appear to get compiled or activated when the submit button is clicked.
Here is some other information:
The /n Software demo directory also includes a web.config file that if I include it in the directory with the directpayment.aspx file, dASP's server will choke on it and generate an error.
I'm hoping that one of you ASP.NET jocks might take a look at what I've done and tell me that I've got my head up my butt and the solution is simple. I'll take my lumps if some of the bleariness in my eyes will go away. /emoticons/smile.gif
Questions:
1) Is there any reason why classic ASP and ASP.NET pages cannot run side by side?
2) Does dASP need to specially configure my account to allow this? Does some kind of virtual directory need to be set up?
3) Any ideas on why my code behind page appears to be ignored?
Again, thank you for your time. Though I'm new to this forum, I promise to come back and contribute. I'm not all take and no give. /emoticons/smile.gif
Kind regards,
David