I have been using the MVC framework now for 3+ months. In fact I already have a public production site running on the framework (www.dimecasts.net). I have to say that I am really, really happy with the progress and direction that the team is making.
But I do have a few things I would like to throw out there as my 'Wish List'
- Do not seal any classes's. There is no need to seal anything. Once you seal stuff you are saying that no-one will EVERY want to make use of this class in a slightly different way.
Examples: AuthorizeAttribute & HandleErrorAttribute.
*** NOTE ***
I have already been told per Scott Gu that this is going to happen in future releases, but just putting my wish out there.
*** NOTE ***
- Try to make as much stuff as possible virtual (overrideable for you VB'ers out there). This will allow us to extend our applications to better meet our needs.
- Make use of more Interfaces. Since testing is really high on the list of priorities for the MVC using more interfaces for classes would simplify mocking and testing.
Example: Anytime a ControllerContext is used (attributes) it is extremely painful to mock these things our for testing.
- Do not become afraid to implement breaking changes
- Keep up the good work. I am really enjoying using this framework as I feel it makes my development experience much better.
So there you go, my simple little wish list for the team. I know it is nothing earth shattering, but I just wanted to get that out there.
Till next time,
[----- Remember to check out DimeCasts.Net -----]
08-05-2008 5:52 AM