Skip to main content

Combining ASP.NET WebForms and ASP.NET MVC

I created a page route to integrate my MVC application with a WebForms page that exist in my project:

public static void RegisterRoutes(RouteCollection routes)
{    
routes.IgnoreRoute("{resource}.axd/{*pathInfo}");    
// register the report route    
routes.MapPageRoute("Reports","Reports","~/Pages/ReportViewer.aspx");    
routes.MapRoute("Default","{controller}/{action}/{id}", new { controller = "Home", action = "Index", id = UrlParameter.Optional });
}

This works when browsing to the specific url’s. However, I noticed this route created a problem whenever I use an  Html.ActionLink in my Views:


<%: Html.ActionLink("Home", "Index", "Home") %>

When I load the page in the browser the link appears like:

http://localhost:12345/reports/test?action=Index&controller=Home

Unfortunately I can't place the route at the bottom, since the webform route has more specific parameters than the MVC route. I was able to solve this problem by introducing a new constraint.

I created a new constraint called IncomingRequestConstraint. This constraint  simply return false for outgoing Urls(so that all Html helpers will work as expected).

public class IncomingRequestConstraint : IRouteConstraint
{
public bool Match(HttpContextBase httpContext, Route route, string parameterName, RouteValueDictionary values, RouteDirection routeDirection)
{
return routeDirection==RouteDirection.IncomingRequest;
}
}

In the global.asax, I added this constraint to the WebForms route:

routes.IgnoreRoute("{resource}.axd/{*pathInfo}");    
// register the report routes    
routes.MapPageRoute("Reports","Reports","~/Pages/ReportViewer.aspx", false, null, new RouteValueDictionary(new { controller = new IncomingRequestConstraint() }));    

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...