8 ms·

Oh man do I feel more and more pushed to upgrade our codebase to MVC4...

by SwearWord 14y ago

phillijw 14y ago
We just did it without too much of a problem. The biggest problems were in the razor syntax
vyrotek 14y ago
I'm curious, is there something specific in MVC4 that you need? Personally, I just want it for WebAPI.
- Encosia 14y ago
  The automatic support for routing to .mobile views is really nice, for one thing. The small improvements to Razor (e.g. automatic ~/ parsing and conditional shortcuts) are also nice time/trouble savers.
  - vyrotek 14y ago
    I've been following MVC for a long time and I somehow completely missed the .mobile.cshtml feature! I can actually make use of this now. Thanks :)
    - jongalloway2 14y ago
      The .mobile.cshtml is included out of the box, but you can also define other specific display modes with a lambda expression: DisplayModeProvider.Instance.Modes.Insert(0, new DefaultDisplayMode("iPhone") { ContextCondition = (context => context.GetOverriddenUserAgent().IndexOf ("iPhone", StringComparison.OrdinalIgnoreCase) >= 0) }); After calling that, you can create a view (index.iphone.cshtml) and it'll be automatically picked up when the condition's matched. This example uses the user agent, but you can use any logic you'd like - cookie / database call / time of day / whatever.
      - vyrotek 14y ago
        Very nice! What's the best way to develop and debug mobile sites locally? Is there a quick way to force either my browser or VS to go into 'mobile' mode? Edit - Found the answer :) http://www.howtogeek.com/113439/how-to-change-your-browsers-user-agent-without-installing-any-extensions/ http://www.howtogeek.com/113439/how-to-change-your-browsers-...
- tugberk 14y ago
  Two of the main reasons are Display Modes and TAP support. Also, you don't need ASP.NET MVC 4 to use ASP.NET Web API. Just install Microsoft.AspNet.WebApi package into your existing ASP.NET MVC 3 project, you will be good to go. Just be careful for the order of routes. Both ASP.NET MVC and Web API routes collected under the same collection and a request may go into another pipeline rather than intended one if routes aren't set up properly.

Oh man do I feel more and more pushed to upgrade our codebase to MVC4...

phillijw 14y ago

We just did it without too much of a problem. The biggest problems were in the razor syntax

vyrotek 14y ago

I'm curious, is there something specific in MVC4 that you need? Personally, I just want it for WebAPI.

Encosia 14y ago
The automatic support for routing to .mobile views is really nice, for one thing. The small improvements to Razor (e.g. automatic ~/ parsing and conditional shortcuts) are also nice time/trouble savers.
- vyrotek 14y ago
  I've been following MVC for a long time and I somehow completely missed the .mobile.cshtml feature! I can actually make use of this now. Thanks :)
  - jongalloway2 14y ago
    The .mobile.cshtml is included out of the box, but you can also define other specific display modes with a lambda expression: DisplayModeProvider.Instance.Modes.Insert(0, new DefaultDisplayMode("iPhone") { ContextCondition = (context => context.GetOverriddenUserAgent().IndexOf ("iPhone", StringComparison.OrdinalIgnoreCase) >= 0) }); After calling that, you can create a view (index.iphone.cshtml) and it'll be automatically picked up when the condition's matched. This example uses the user agent, but you can use any logic you'd like - cookie / database call / time of day / whatever.
    - vyrotek 14y ago
      Very nice! What's the best way to develop and debug mobile sites locally? Is there a quick way to force either my browser or VS to go into 'mobile' mode? Edit - Found the answer :) http://www.howtogeek.com/113439/how-to-change-your-browsers-user-agent-without-installing-any-extensions/ http://www.howtogeek.com/113439/how-to-change-your-browsers-...
tugberk 14y ago
Two of the main reasons are Display Modes and TAP support. Also, you don't need ASP.NET MVC 4 to use ASP.NET Web API. Just install Microsoft.AspNet.WebApi package into your existing ASP.NET MVC 3 project, you will be good to go. Just be careful for the order of routes. Both ASP.NET MVC and Web API routes collected under the same collection and a request may go into another pipeline rather than intended one if routes aren't set up properly.