Areas in MVC / .NET

[envo]

This is an interesting issue and was wondering if someone could shed some light on it.

Using Visual Studio 2013 Professional, I create a new project.

Choose Visual Basic, then Web, then Web Application. I choose MVC. No Authentication. Create.

Then I add an Area called "Test". A Controller called "Test" and a view called "Index".

I hit F5, project builds and runs and gives me HTTP 404

I do THE EXACT SAME THING (literally the same steps), except choose C# instead of Visual Basic when creating the Web Application. And it works.

My question is: WHY!!!!

 

[semaphore]

Coz its VB

 

[envo]

Coz its VB

Yes, but you'd think it'd work out the box like c#? I'm required to add Areas to our existing MVC application that's written in VB, and for the life of me can't figure out why there's such a difference. Area Registration happens, but never hits the controller

 

[Frikkenator]

Is it not perhaps something different between the VB and C# RouteConfig templates? Compare the two and see if they're the same.

 

[envo]

Is it not perhaps something different between the VB and C# RouteConfig templates? Compare the two and see if they're the same.

Did that, no difference

 

[semaphore]

Test does end with TestController right?

 

[semaphore]

You're doing something wrong.

http://localhost:42377/Test/Index/

mine works fine