ASP.Net Core Areas

You don't have to add the area name to the pattern in your conventional routing. it's often a good idea to do so, especially for clarity and consistency. When you look at the route pattern, it's immediately clear which area the route belongs to. This makes it easier to understand and debug your application. If all your routes have the area name in the pattern, it provides a consistent approach, making your code easier to maintain. If you have routes with the same names in different areas, adding the area name to the pattern ensures that there are no naming conflicts.

1. Including Area Name in the Pattern:

app.MapAreaControllerRoute(
    name: "blog",
    areaName: "Blog",
    pattern: "blog/{controller}/{action}/{id?}"
);

Pros: Clearer, consistent, prevents potential conflicts.
Cons: Slightly more verbose.
2. Not Including Area Name in the Pattern:

app.MapAreaControllerRoute(
    name: "blog",
    areaName: "Blog",
    pattern: "{controller}/{action}/{id?}"
);

Pros: Less verbose.
Cons: Less clear about the route's area, potential conflicts if similar routes exist in other areas.

app.MapAreaControllerRoute( name : "blog", areaName : "Blog", pattern : "{controller}/{action}/{id?}" ); app.MapAreaControllerRoute( name: "Zebra", areaName: "Zebra", pattern: "{controller}/{action}/{id?}" );

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Tuhin Paul1y ago
Accepted answer
You don't have to add the area name to the pattern in your conventional routing. it's often a good idea to do so, especially for clarity and consistency. When you look at the route pattern, it's immediately clear which area the route belongs to. This makes it easier to understand and debug your application. If all your routes have the area name in the pattern, it provides a consistent approach, making your code easier to maintain. If you have routes with the same names in different areas, adding the area name to the pattern ensures that there are no naming conflicts.

1. Including Area Name in the Pattern:
```
app.MapAreaControllerRoute(
    name: "blog",
    areaName: "Blog",
    pattern: "blog/{controller}/{action}/{id?}"
);
```
Pros: Clearer, consistent, prevents potential conflicts.
Cons: Slightly more verbose.
2. Not Including Area Name in the Pattern:
```
app.MapAreaControllerRoute(
    name: "blog",
    areaName: "Blog",
    pattern: "{controller}/{action}/{id?}"
);
```
Pros: Less verbose.
Cons: Less clear about the route's area, potential conflicts if similar routes exist in other areas.
+2

mina shaker1y ago

@Tuhin Paul but when i did it like below code as you can see the pattern is the same no area spacifaied this where the conflicts come into place correct?