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

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

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.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...