Skip to main content

ASP.NET MVC 3 is getting closer…

Time goes fast and for the ASP.NET MVC team it even goes faster. I just figured out most of the features inside ASP.NET MVC 2 and version 3 is already showing up.

So what's new in ASP.NET MVC 3?

  • Razor Syntax View Engine - Cleaner view syntax
  • Dynamic View and ViewModel properties - passing data between controllers and views using dynamic rather than a dictionary
  • "Add View" Dialog Box Supports Multiple View Engines - You two can be in this box.
  • Service Location and Dependency Injection Support - Get your DI hooked into controller factories, dependency injection, action filters and View Pages.
  • Global Filters - put filters on the all control methods
  • New JsonValueProviderFactory Class - Model bind directly to JSON-encoded data
  • Support for .NET Framework 4 Validation Attributes and IValidatableObject - Easier validation including validating one property based on another.
  • New IClientValidatable Interface - Discovering at runtime if the client supports validation.
  • Support for .NET Framework 4 Metadata Attributes - Support .NET 4 specific attributes like DisplayAttribute
  • New IMetadataAware Interface - Write your own attributes to contribute to the ModelMetadata creation process.
  • New Action Result Types - HttpNotFoundResult, HttpStatusCodeResult.
  • Permanent Redirect - More easily return 301s for Actions, Routes or any URL.

Read more about it:

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more