First of all, the term "MVC" has two related meanings. First is the architectural pattern, and second is the framework over ASP.NET implementing this pattern. Please see:
http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller[
^],
http://www.asp.net/mvc[
^].
What are we talking about. If it's about the architectural pattern, the Solution 2 tells you that in principle you may not lean C# and .NET. But this is a kind of casuistic which hardly can help you with your intentions: instead of learning C# and .NET with ASP.NET, you would need to learn something else, most likely no less that that. But please see my notes on the real knowledge level you really need to achieve, in my second last paragraph ("In fact, your suggestion…", and so on).
"Possible" and "impossible" and also "to learn" (to learn — to what extent?) are pretty much relative categories. Let me put it this way: this is nearly the worst idea possible. The most important problem is your attitude: are you trying to save your time on learning? If so, I have much better idea: abandon the profession, any engineering profession. It's for people who are eager to learn, especially the fundamentals, not for those who wish to save on it and get to right to results. Nobody need such "results".
In fact, your suggestion that learning C# and .NET might be important is highly minimized. You really need to learn order of magnitude more that that. It includes, but not limited to, understanding of networking, major protocols and the whole protocol model, HTTP in particular, understanding of Web operation, JavaScript (and this is a big part of technology), general programming, some major algorithms, good part of .NET FCL, HTML, CSS and, the last but not least, industrial design and UI design skills.
Thank you for understanding.
—SA