As for the degree not matching a developer role, you could pick 2 or 3 courses and put a highlights section under it that may be useful though this is for specific points rather than general things which is likely one of the bigger issues with your resume. What were the best parts that you did? What are the key points to know? That you "Obtain and complete tasks" is about as good as saying, "I breathe and ingest food." Did you do any planning of the tasks? Did you do particularly well with particular kind of tasks? Did you tasks include specific components that may be a highlight?
Are you sure people would tell others that you are doing really well? Some people may be polite to you but tell others another story. Something else to consider is how well do your colleagues know how good you are compared to other companies and cultures. The best at Microsoft or Google may be quite different than where you work at the moment if you want another idea here.
If you really want to show the fast learning, do a pet project on your own where you learn something relatively quick that you can discuss in a cover letter or interview. Keep in mind what kind of expectations you are communicating here. Are you implying that you could learn how to reverse engineer Visual Studio in 2 days or less? How deeply do you know your current languages? Do you know all the different versions of the .Net framework and its history,e.g. 1.0, 1.1, 2.0, 3.0, 3.5, 4.0 and so forth?
Some people may dabble in various areas and thus could have a wide range of experiences before being professionally employed. In entering university, I had programmed on my Commodore 64, Watcom BASIC, Watcom Pascal, assembler on a Commodore Pet, and done some programming with gates on a bread board either on my own or in high school courses. In university I had exposure to more versions of Pascal, Modula-3, Scheme, C/C++, Matlab, and Maple in addition to learning about HTML on my own. In addition there is something to be said for how much experience can one have and still be seen as junior which can be a few years.
The C# you know do you know all the different ways it can be used: Winforms, Webforms, ASP.Net MVC, console applications, WCF services, WPF, Windows Services, and Workflow Foundation? How certain are you of the complexity of ASP.Net MVC framework if you've never used it? Would you be able to build your own version over a weekend? This is something to consider that you say fast and a company may think, "Ah, get it done in 2 hours," which isn't quite what you meant by fast.
You communicate what you mean by "learn fast" in giving examples of where you've done this. What evidence do you have for that claim? Do you have proof of this or do you just believe this without any proof that would convince someone?
Be careful how you handle critics as that may cause more issues since if someone is a little hostile to you that you offer childish antics? What you state here is what will be used here. You aren't the administrator of this site so be careful of how mighty you think you are.