routing

I'm at a loss as to why my routes are conflicting. I have these in my Global.asax file: routes.MapRoute( "CustomerView", "{controller}/{action}/{username}", new { controller = "Home", action = "Index", username = "" } ); routes.MapRoute( "Default", "{controller}/{action}/{id}", new { controller = "Home", action = "Index", id = "0" } ); So far everything has worked fine except when I created a controller action like so: public ActionResult MyAction(int id) { //Do stuff here return View(); } When I try viewing it through http://mydomain/MyController/MyAction/5 I get: Server Error in '/'

It's most common practice to register routes in Application_Start event within global.asax.cs/vb file. But you need to have access to this file to do so. Fine. I either don't have or don't want to. I'm trying to integrate Asp.net MVC application into a Sharepoint 2010 site and don't want to create my custom global application class that would also register routes for me and change the Sharepoint's Global.asax file and put a different class definition in it. My application wouldn't be accepted because I would be doing unsupported things to Sharepoint. I was wondering if it was possible to

I am using Django 2.0 and now I have no idea how to make an 'empty' url for the homepage. Meaning, I want it to route for web.com/ or web.com . I tried this code but it does not work: urlpatterns = [ path('admin/', admin.site.urls), path('/', include('post.urls')) ] ...and post.urls urlpatterns = [ path('', views.index, name='index') ] And the error I get when I make a request to localhost:8000 : Request URL: http://localhost:8000/ Using the URLconf defined in myblog.urls, Django tried these URL patterns, in this order: admin/ / The empty path didn't match any of these. I did sort of find a

I want all URLs in my application to have a trailing slash. I have the following route in my route.yml: foo_route: pattern: /foo/{page}/ defaults: { _controller: FooBundle:Foo:list, page: 1 } requirements: page: \d+ Requests to '/foo/1/' work fine, however requests to '/foo/' are not matched because of the trailing slash in the URL pattern. How can I define routes with trailing slashes and an optional parameter? I am aware I can define 2 different routes for the two cases, but I want to avoid that. In a separate but related case, you can match the following three patterns: /foo /foo/ /foo/page

I've just upgraded to Rails 4 and found an unexpected behaviour with routing. We have a controller named EmailPreviewController. The routing for this was: get "/emailpreview", controller: 'EmailPreview', action: :index however after upgrading to Rails 4 this throws the following error when the environment is loaded: 'EmailPreview' is not a supported controller name. This can lead to potential routing problems. See http://guides.rubyonrails.org/routing.html#specifying-a-controller-to-use I've looked at the page it suggests however there isn't any indication that it's incorrect to use a

I want to have multiple routing modules in order to keep my application clean and easy to read. I currently use lazy loading for the SubComponent but I don't want to do this. So I am looking for a way to change this. Anyways, here is the currently working code. I have the following two routing files. app-routing.module.ts : import { NgModule } from '@angular/core'; import { Routes, RouterModule } from '@angular/router'; const routes: Routes = [ { path: '', component: HomeComponent }, { path: 'sub', loadChildren: './sub/sub.module#SubModule' } ]; @NgModule({ imports: [RouterModule.forRoot