There are times when you want to run regular code on your SharePoint server. The SharePoint site runs through a ISAPI filter that intercepts all traffic to the particular port a SharePoint site is located. The filter then works it magic on the request and send it back to IIS for shipping. This presents a problem when you want to run classic ASP, ASPX, PHP or any other scripting language. This tutorial will walk you through the steps to get your SharePoint site to play nice with your scripting code.
- On the server create a folder (example: "c:\non_sp_code"). This will be where your non-SharePoint code will call home. Create hello_world.asp (or whatever) file here.
- From IIS manager right click your SharePoint site > New > Virtual Directory.
- Complete the Virtual Directory Creation Wizard (this is where your code will live virtually).
- Virtual Directory Alias = "My_New_Virtual_Directory"
- Web Site Content Directory = "c:\non_sp_code"
- Fill out the rest of the wizard as appropriate.
- Go to Start > All Programs > Administrative Tools > SharePoint Central Administration.
- Select "Configure virtual server settings" > "Default Web site" > "Define managed paths"
- In the "Add a New Path" Section at the bottom of the page, type the virtual path such as "/My_New_Virtual_Directory".
- Select the "Excluded path" radio button and click Ok.
- To test go to http://www.mydomain.com/My_New_Vitual_Directory/hello_world.asp.
Basically what you have told the SharePoint ISAPI NOT to process this directory and allow IIS to handle the files with the appropriate Web Service Extension handler.
Note: You may have to enable the particular Web Service Extension from the IIS snap in > Web Service Extensions > Active Server Pages (for classic ASP code) > Allow.