Here's the rub:-
I have authored a database/content managed web site completely written in C# & ASP.NET that uses MS Access for data store.
The web host does not allow third party COM registration.
There is an online payment facility that has to be HTTPS. Only ASP & script is allowed inside this secure area. The page was originally written in ASPX using a server side control to manage the gateway to the merchant account.
So, I have converted the ASPX payment web form over to ASP code with some VBScript replacing the codebehind .NET code. I have also generated type libraries for the C#.NET classes that all the ASPX pages use - reason being I really would like to use these existing assemblies to manage the ASP payments page. All works, but only when the .NET assembly that has the COM interface is registered on the web server.
In my relatively minor experience of HTTPS and even lesser experience of ASP 3 & Windows Scripting, is there any way that my ASP page could use "CreateObject" etc. to instantiate the .NET assembly? Like I said, the host will not allow any COM to be registered so even by making a .NET assembly INTEROPerable like has been done is not going to work.
Or in other words, is there any way that an ActiveX dll can be instantiated without being in the registry?
(Fallen at the last hurdle are the words that spring to mind!!)
Many thanks,
Glyn.
I have authored a database/content managed web site completely written in C# & ASP.NET that uses MS Access for data store.
The web host does not allow third party COM registration.
There is an online payment facility that has to be HTTPS. Only ASP & script is allowed inside this secure area. The page was originally written in ASPX using a server side control to manage the gateway to the merchant account.
So, I have converted the ASPX payment web form over to ASP code with some VBScript replacing the codebehind .NET code. I have also generated type libraries for the C#.NET classes that all the ASPX pages use - reason being I really would like to use these existing assemblies to manage the ASP payments page. All works, but only when the .NET assembly that has the COM interface is registered on the web server.
In my relatively minor experience of HTTPS and even lesser experience of ASP 3 & Windows Scripting, is there any way that my ASP page could use "CreateObject" etc. to instantiate the .NET assembly? Like I said, the host will not allow any COM to be registered so even by making a .NET assembly INTEROPerable like has been done is not going to work.
Or in other words, is there any way that an ActiveX dll can be instantiated without being in the registry?
(Fallen at the last hurdle are the words that spring to mind!!)
Many thanks,
Glyn.
