I'm not saying it's not good idea.
It's a trade-off between getting project going quickly, using tools that framework has provided, or having to write your own layer for cross layer communication to stay completely framework independent.
For you that independency might be most important measurement for codebase, while for me, I am more concerned with quick results, so I'm ok relaying on framework tools and libraries. Neither approach is wrong, but it has to be right approach for each individual project.
Is this your first MVC project?
I've seen couple of tutorials out there, but to be completely honest, unless you start working on an actual project, it's very hard to grasp the concept from just reading tutorials. I'd say there's nothing better than getting your hands dirty and doing a little mock project first, if you don't want to commit to a framework just yet.
