How long has ASP.NET MVC been widely used in industry?

Question

I am trying to decide whether to learn ASP.NET MVC (or spend time learning another technology that interests me). I know that this is an elegant design, but I try to evaluate my future job opportunities if I invest in this skill. In your estimation, how long will it be before the demand for competitors' ASP.NET MVC developers, what for developers in other top web developers? Is this the question of the year? 2 years? 3+? In the corresponding note, do you see that using ASP.NET MVC is superior to classic ASP.NET in the foreseeable future? Scott Guthrie says they will exist side by side, but I'm curious how much attention ASP.NET MVC will share.

I know this is a speculative question; I'm just interested in your subjective judgments.

Answer 1

For the main implementation, I would not expect it to really take off only after RTM. Initially, the work will be limited to new projects, which, I suspect, may be smaller than the economy. Real job growth will come when better-known projects requiring maintenance are created.

As for surpassing the original ASP.NET, this will happen when older projects are decommissioned, either in one stroke, or with the replacement of partitions with new MVC functions.

Personally, I would study at least the basics now, to be prepared for an increase after RTM.

Answer 2

"but I'm trying to gauge my future job opportunities if I invest in this skill."

If you want to increase your future job opportunities, then what you should rather ask yourself; "What a hysterically cool and fun thing I could work on today?"

Because if you think about “what makes you valuable,” you will always be mediocre. If you, nevertheless, do what FUN does, you end up creating competency, few others have the ability to excel - which always seems valuable in the world ...;)

Not to mention that your professional life will be much better!

Do what FUN and what you get from the “kicks”, then your “value” will increase!

Answer 3

I know that some companies, including my own, adapt to asp.net mvc and use it for almost all projects.

Despite the fact that this is a beta version, I still see it widely used. This is probably due to the fact that ASP.NET is such a strong web language, companies are increasingly adapting to better and more advanced technologies such as .net.

Answer 4

At our company, it is becoming the de facto standard for new projects, and we are currently in the middle of migrating our main site from ColdFusion Mach-II to ASP.NET MVC, as both are MVC environments and I see MVC as excellent Architectural template for web forms and code models.

Given that Microsoft spent a lot of time and effort on this, I don’t think it will disappear by any means, especially when you have interesting things like IronRuby.

Answer 5

I think both options will be over time.

The current trend seems to apply to RESTful apps, etc., and I expect MVC to gain popularity. However, some projects are more suited to the existing web form style, while others will benefit more from MVC.

MVC is great, and learning the basics won't take long. Go through Scott Guthrie's blog tutorials (although some of the earlier materials are outdated and the syntax has changes)

MVC has some disadvantages:

MVC does not use viewstate. It has positive (smaller pages, faster, cleaner model) and negative points. Although this is not impossible, it is more difficult to develop elements such as controls that need to maintain state, for example. paging datagrid etc.

Many companies already have investments in existing web form technologies.

Answer 6

I also know some regular companies that are already developing in it, and some that are considering its use. I think that this is already at the stage when a regular asp.net programmer would be wise to mess with it.

Answer 7

We will use it for our next project. Before releasing a project, RTM is not required with it. He just needs to go through the QA.