Should I migrate from symfony 2 to Asp.Net MVC?

Question

symfony

Friends, we need your help.
I have been working on the web for 5 years, exclusively backend on php. I tried different hfp frameworks: zend 1, kohana 3, yii 1/2 and the last one - laravel 5. In principle, they are all of the same order with a “hard frame”, problems with which begin when the project grows. For example, in the same laravel:
We use the Repository pattern as a wrapper for Eloquent to hide the query builders. As a result, the methods return Eloquent models, which must be used as DTOs in order not to violate the single responsibility principle, if possible. The models themselves are not viable in the future, because they are rigidly inherited from Eloquent, and if we move part of the data to another storage, then we will have to pervert by replacing the models through IoC in order to map the data to them. As a result, it all rolls into a wild srach or magic in the project, which you have to keep in mind.
And now the hands have reached the Symfony 2 framework, which is positioned as an enterprise. I looked at it in an overview, and it seems that all the hemorrhoids of the voiced frameworks are solved in it. And the question arose whether it was worth learning this framework at all. All literature on patterns, techniques, refactoring, etc. is written with examples in C# or Java. It is difficult for me to read and understand the material without knowing the syntax of these languages. But knowing, for example, C#, will php be needed at all if there is Asp.Net MVC.
So there were questions about Asp.Net MVC:
1. Is it difficult to develop on it and upgrade to new versions, because it has been developing wildly in recent years?
2. How expensive and difficult will it be to maintain a project, for example, an online store (Wikimart level), relative to the symfony + mysql bundle?
3. In your experienced opinion, is it worth moving to C# given the release of php 7? Will it be like a step of professional development and skills development in the future? It's hard for me to answer this question myself, because I don't know Sharpe.

Answer 1

Climbed with Yii, no regrets. It's a pity Symphony never looked.
1. Is it difficult to develop on it and upgrade to new versions, because it has been developing wildly in recent years?
As usual - complex projects, where a lot of links to "I don't know what" are difficult, small projects where you can seriously refactor everything in a day is easy.
2. How expensive and difficult will it be to maintain a project, for example, an online store (Wikimart level), relative to the symfony + mysql bundle?
Don't know. It seems like the specialists are more expensive, but mysql and the DBMS are not the best, like it has been omitted lately and postgres is recommended from the free ones. Yes, I myself decently suffered with mysql while restoring innodb tables. So it seems to me that it will be cheaper on ASP NET MVC, because it is done faster, it is better supported, and again, less hardware is needed. And there are a lot of vacancies in PHP with a salary> 100k, so they are not so cheap. Students should not be trusted to write wikimarts.
3. In your experienced opinion, is it worth moving to C# given the release of php 7? Will it be like a step of professional development and skills development in the future? It's hard for me to answer this question myself, because I don't know Sharpe.
The only thing I know about php7 is that they will tighten up the typing a bit. I myself still write a little in PHP, I support a couple of my own stores on Yii. And so I will tell that all the same C# is more pleasant. What a nicer language. The VS + re# development environment is in no way inferior to phpstorm, even more abruptly, because suggests more readily. There are more language features and less magic in the code. After all, when the project is being built, it’s somehow calmer in my soul :) It’s easier to refactor. RE# also keeps the views in check (wide solution analysis).
I also like the way it works with libs. PHP composer is used, and all these libs are with the source code. You need to transfer the project, it can be about 10,000 files (it is clear that), and in C # everything is packed into a DLL. If you have already used a class in the studio, then it will work, then it is connected here, but in PHP with its auto_load it’s not a fact, the IDE just knows that such a class is in the project and prompts.
In C#, it is more convenient to separate layers. For example, I took DAL into a separate project, I stupidly check the dependency on the project in others, I use the same code in the console for development (all kinds of data exports between databases) in the public part, in the closed part. And all this is easy, within the framework of the solution. In puff, probably a little tambourine is needed for this (I honestly don’t know, there was no need).
Here they also wrote about EF that they say the only ORM. I disagree, there are too many. Active records are an evil thing, they are heavy and provoke work with the database spread throughout the project.

Answer 2

worth moving. I have been programming in PHP for 2.5 years, including Zend 2 and Symphony 2 ..... and then 3 years in Sea Sharp and in particular in MVC ..... heaven and earth.
and php 6-7 has been promised for 10 years already ...... I also once waited for it)
after the first month of development you start to think - why did you waste so much time on php ???????
about the prices for projects - hostings are practically the same, well, windows can be 5-10 percent more expensive and not everywhere.
for the development of sites even at the corporate level, a free visual studio is more than enough .... and even this one outdoes all the PHP IDEs put together .....