In order to install the Isis ASP.NET Control Panel in an application, currently you need to have Routing installed. If you're using .NET 4, simply add a reference to System.Web.Routing and rebuild your application. If you're using ASP.NET MVC (any version) you should already have routing referenced and set up correctly in your global.asax file. If this is a web forms application, then you will need to add the following to your global.asax:

public class Global : System.Web.HttpApplication
{
void Application_Start(object sender, EventArgs e)
{
RegisterRoutes(RouteTable.Routes);
}

public static void RegisterRoutes(RouteCollection routes)
{
var isisHandler = new IsisRoutingHandler();
routes.Add(new Route("isis", isisHandler));
routes.Add(new Route("isis/{controller}", isisHandler));
routes.Add(new Route("isis/{controller}/{action}", isisHandler));
routes.Add(new Route("isis/{controller}/{action}/{parameter}", isisHandler));
}

}

Finally, in your web.config, assuming you are running on IIS7 (integrated mode), you will want to include the following:
<system.webServer>
<validation validateIntegratedModeConfiguration="false"/>
<modules runAllManagedModulesForAllRequests="true">
<remove name="UrlRoutingModule"/>
<add name="UrlRoutingModule" type="System.Web.Routing.UrlRoutingModule, System.Web,

Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
</modules>
</system.webServer>

Removing and re-adding the routing module might not be required, but the key part here is the runAllManagedModulesForAllRequests="true". If you don't have that set, you'll probably get a 404 when you try to navigate to your control panel.

Last edited Feb 2, 2011 at 8:23 PM by ssmith, version 1

Comments

No comments yet.