Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

I am a lover of ASP.NET MVC and a hater of ASP.NET Webforms, so I am always looking for a job where they use MVC. But here firms are usually not using MVC . Also I am not good in Webforms and really, really hate html, css and js abstractions which generate annoying output. My feelings tell me that I will not be successful in projects that use frameworks I hate.

Should framework choice be decisive for job selections? Do I have to change my negative thoughts on Webforms and try to improve myself on it? Or it is really better to look MVC jobs?

Do you care what framework and framework versions are in job postings? Can you also share your experiences in jobs where they were using frameworks that you hated?

share|improve this question

closed as off-topic by gnat, BЈовић, MichaelT, Kilian Foth, Dan Pichelman Aug 7 '13 at 15:42

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions seeking career or education advice are off topic on Programmers. They are only meaningful to the asker and do not generate lasting value for the broader programming community. Furthermore, in most cases, any answer is going to be a subjective opinion that may not take into account all the nuances of a (your) particular circumstance." – gnat, BЈовић, MichaelT
If this question can be reworded to fit the rules in the help center, please edit the question.

    
MVC isn't the right tool for every job. It's great for some types of sites. For other sites (where the app is more like a winform app) it's better to use standard webforms and heavy use of ajax techniques. –  CaffGeek Aug 29 '11 at 14:46
add comment

4 Answers 4

up vote 4 down vote accepted

I've been trying to spot a job using ASP.NET MVC in my local market (Germany) but couldn't find a single one. Everyone uses WebForms.

I think this is due to the fact that a whole lot of companies invested heavily in development of their products and they won't go anywhere else even provided a better option, so they're looking for a programmer to support their [legacy] code.

Another reason is that for web software which is more of a "web application" rather than of a "web site" type MVC with all of the manual work required is a wrong tool for the job. Close the eyes, bring to memory the UI of SAP products, various ERP and CRM packages and imagine how hard it would be to bind all that multitude of controls manually with JavaScript. If you're looking at enterprise jobs, that's the problem they will all have with MVC.

I've also observed that the programmers of those companies even when talking unrelated to the company work don't show much interest in ASP.NET MVC. But hey, we all know it's hard to find enthusiastic people everywhere.

So no particular advice for you except for keep looking and look in the direction other than enterprise products.

share|improve this answer
1  
Even in Germany companies has followed new technologies heavily huhh. I am currently using ASP.NET MVC 3 and Entity Framework 4.1 code first in my job sure the product is new not old. But i am not comfortable in current job because of another reasons. Thanks for answer –  AnyOne May 8 '11 at 17:09
add comment

I recently started a new job, in my search I had the exact same problem as you. I wanted to avoid ASP.NET Web Forms.

A lot of companies don't know the difference, they only know '.NET' or perhaps 'ASP.NET'. Lots of doing the hiring and especially job agencies don't know the difference between MVC and Web Forms. For this reason it's important that you get to speak with someone who does know the distinction. For some job openings I made sure I knew before even agreeing to come to an interview.

Some potential employers may attempt to sidestep the issue, let them know you are serious about it.

If anything perhaps learn how to do a Web Forms and MVC hybrid, learn enough about Web Forms that would allow you to work on a transition. Perhaps you can find an opening somewhere where they build new stuff in MVC.

Another option is picking a company where you'll be the only (web) developer. No one will care what you use, just as long as it works...

share|improve this answer
3  
I've found that sidestepping techniques usually end up sounding like "That's something we want/plan/intend to use or move into in the future" ie. "We aren't doing it, and we probably never will." –  Steve Evers May 8 '11 at 21:06
add comment

As mentioned by @Developer Art not every company will switch to a new API just because it is more fancy. Most of companies have their SW already shipped and they have to maintain and extend a large code base. There is no reason to shift to a new technology and invest enormous amount of money to change the core technology of the product without adding new features. There are still products which haven't been still migrated from old ASP + VBScript. Another story is that MVC doesn't have to be suitable for everything.

Even joining big company with a lot of internal development doesn't solve this. I have my own experience where we were forced to use crappy internal framework based on crippled (yes it is really possible to make web forms even worse) ASP.NET 2.0 + Data sets.

If you want to do MVC your best choice are either startups where people have a choice to use a new technology, companies starting a new project which should use a new technology (you usually need insider to now about that) or consultancy / software houses developing business application on demand - these projects can be 3-12 months and developers usually chose technology they want to use.

share|improve this answer
add comment

I would say it's good to want a job using new technology. Sure, maintenance is always a looming shadow but the way our field changes, you must evolve or perish. I've heard of the horror (and been subjected to it myself) of companies that are stuck in the stone age of technology, blissfully ignorant of anything that has happened in the past 10 years or more. These places are great if you want to wind down and count the years until your retirement, but a living hell for anyone passionate about their craft.

MVC is the coming thing. WebForms will stay around for a while, this is true, but most high-end .NET developers are solidly behind using MVC for all future development. If you care about your craft then it's a good thing to pursue a job using the stack you want; don't starve to death while doing it, however. If you have to take a WebForms job and hold your nose through the stink long enough to find a cutting-edge job then do it.

share|improve this answer
add comment

Not the answer you're looking for? Browse other questions tagged or ask your own question.