Map a Virtual Directory to the 'webdashboard' subfolder of your ccnet folder. Enter the location of the aspnet_isapi.dll file you use. Make sure Script engine is checked and check that file exists is not check ed.
Map a Virtual Directory to the 'webdashboard' subfolder of your ccnet folder. Enter the location of the aspnet_isapi.dll file you use. Make sure Script engine is checked and check that file exists is not check ed.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as TXT, PDF, TXT or read online from Scribd
Map a Virtual Directory to the 'webdashboard' subfolder of your ccnet folder. Enter the location of the aspnet_isapi.dll file you use. Make sure Script engine is checked and check that file exists is not check ed.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as TXT, PDF, TXT or read online from Scribd
Map a virtual directory to the 'webdashboard' subfolder of your CCNet folder
(typically called ccnet) 2. In the configuration for this virtual directory, click the Configuration b utton of the Virtual Directory tab 3. Click Add to add a new Application Mapping 4. In Executable, enter the location of the aspnet_isapi.dll file you use (lo ok at the .aspx mapping as an example. A typical value would be c:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspn et_isapi.dll for CruiseControl.NET release 1.2.1 or earlier, or c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll for late r releases) 5. In Extension, enter .xml 6. Make sure Script engine is checked and Check that file exists is not check ed 7. Click O as necessary to save your changes 8. Under the Virtual Directory's Documents tab make sure that default.aspx is added as a default document Incase of "Page cannot be found" error The security settings in Windows 2003, prohibits ASP.NET ISAPI. Here is how you should solve this 1. Click on "Web Service Extensions" in IIS 2. Select "All unknown ISAPI extensions" 3. Click on "Allow" 4. Select "ASP.NET vx.x" 5. Click on "Allow"