Join us this Friday for AI in Action at the Virtual Happy Hour! This free virtual event is open to all—enroll now on Academy and don’t miss out.
Join us this Friday for AI in Action at the Virtual Happy Hour! This free virtual event is open to all—enroll now on Academy and don’t miss out.
Hi Uyen
I don't think you need to specify a namespace constraint for the routes in this case. If you move the controllers to another assembly, and they are all available for the web project, everything should be fine.
The namespace constraint is more useful when you have more than one controller with the same name, but in different namespaces. In that case you can use this constraint to define different routes with different controllers.
Hi,
Iam trying to separate the controllers into a separate project. How do i modify the routing to handle this.
I know in MVC you can add a namespace parameter to the routing, is that possible with EPiServers MapContentRoute?
Any ideas?
Thanks