RTC Forums
April 19, 2024, 09:49:38 PM *
Welcome, Guest. Please login or register.

Login with username, password and session length
 
   Home   Help Login Register  
Pages: [1]
  Print  
Author Topic: Running a Visual WebGUI ISAPI dll under RTC demo Web Server  (Read 3106 times)
wbroyles
RTC Expired
*
Posts: 21


« on: May 06, 2014, 10:19:59 PM »

Trying to run a Visual WebGUI system using the demo web server application. The index form is embedded in the DLL not sure how to specify this.
A normally link would look like this https://www.curopro.net/form1.ashx. Form1.ashx is our index form.

Any help on configuration would be helpful.

Thanks

Wade
Logged
D.Tkalcec (RTC)
Administrator
*****
Posts: 1881


« Reply #1 on: May 07, 2014, 09:14:43 AM »

RTC Demo WebServer comes with an example Data Provider for handling ISAPI extensions, which is implemented in two units located inside the Demos\DataProviders folder.

In the rtcISAPIProvider unit, inside the ProviderCheckRequest method, all ISAPI DLL requests are accepted, the Request.FileName property is modified and the Request.Info[] parameters "Root", "DLL" and "PATH" are prepared for use by the ISAPI handling code, which is implemented in the rtcISAPI unit.

The default implementation expects you to specify an extension for ISAPI DLLs and include the relative path to the DLL along with the name of the DLL when sending a request to the Server. If you want the DLL to be accessible through the root URI, you need to change that behavior in the rtcISAPIProvider unit.

Please note that the implementation for handling ISAPI extensions, as well as the WebServer Demo Project, are just examples. They are not part of the SDK, so you should make your own copy of all the files used in that Project, including files from the "DataProviders" folder, and modify them to suit your needs.

Best Regards,
Danijel Tkalcec
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!
Page created in 0.022 seconds with 16 queries.