Webform? HTML + ashx? MVC?
Always struggle, choose which, I am a self-taught. Net, the beginning is contact webform, saw many webform video, but found that project to do webfrom form submission way always blinked in a cause page refresh the page, the user experience is very bad, and feeling server controls are not good, most of the time or in the use of HTML controls,
Then can know with JQ ajax asynchronous submission data, using ashx generally receive handler, return after processing, page does not refresh, a project down. Aspx file background completely didn't write what code, simply use HTML file instead of it, the multiple projects has always been HTML page + ashx,
Slowly feeling, but also the original HTML page is bloated (especially after a few WPF project experienced MVVM development mode and the reusability of good custom controls), in thinking, whether should study the web MVC development mode, and then when I found that after practice the habit can't completely MVC, built a MVC project, found that there is a will refresh the page to submit data (although seem not flashing? , and then continued with JQ ajax submit data to the controller, it makes me feel and HTML + ashx nothing different ~
As above, now is good, with which, baidu to check a lot, like HTML + ashx is considered by the industry is very low, a way of development, mostly MVC or recommend?

CodePudding user response:

What type of project, if the website is the enterprise management system, the webform can
If it is web 2.0 sites, you can use the MVC

CodePudding user response:

Very low, not the technology, is very low, is your company's work

Normal, either you aspire to become a front-end, or aspires to be the back-end,
Why do you feel uncomfortable, because your side for a bit, there for a bit, you are back and forth, like painting, painting is the man who is layered, step, back and forth from the start each trace eyes
Yeah, the way you now so, tracing the eyes back and forth, ahead to data, ran back to get it, got to get the data before running back

In front of the MVVM yeah, vuejs, anglar, knockout, react, but he is not for you, he is suitable for the people aspire to do front end,

CodePudding user response:

Suggest you use ASP.NET Core Blazor, a c # version of the presents

CodePudding user response:

Many people here are reply
"I don't need those things I'm not a BAT,"

If you don't change the way we work, you will never be BAT,

The reason is simple:
1. The focus in the front-end and back-end focus, do back and forth, back and forth is equivalent to jet lag
2. The front nine into 9 ajax to work is not what you said, post, and they are 9 into 9 work so get cool Fried day, so friendly interaction, so smooth loading
3. The back-end began to feel very relaxed, but don't happy, since that part of the work hand over to you, so please consider how to make your backend is more stable, logical process, better scalability, concurrency more
4. The front end to do good, users prefer to use, use more, he will be back end reversed transmission you, so don't want to BAT no, collapsed in the middle of the night, hang up is who? Your front end will be reversed transmission you go play, BAT you mouth that those who are doing, your bosses, planning, product managers will also force you BAT drops, because something good, more users, they will think about how to get more NX bit

CodePudding user response:

Webform? Simple and easy to use, to learn the cost is low, the front-end code generation more

HTML + ashx? Simple and easy to use, the study of low cost, less front-end code, the performance is better than the former

MVC? Not easy to fit in the point of adult learning, function is easy to implement async, convenient extension, support plug-in also many, performance controllable

CodePudding user response:

Want to simple, choose webform? Because there are many privileges or buttons to control show hidden

If must use HTML + ashx? Have to solve the problem of authority, because HTML show hidden with the server is not the same as

Of course many extensions are main MVC? Are now in use web API,.net core, feel the new technology, but that are going to study cost, time cost, the personnel ability...

CodePudding user response:

I think the first summarizes the main points of the problem,

Read your description, you are using the web form is met when the HTML file bloated problem, the root of the problem is not in the web form framework, separate multiple files to write, or make it controls the reusable parts can be solve,

Is your problems when using the MVC page will refresh, this has nothing to do with the MVC this framework is also, you use ajax to submit a request, in the framework of MVC, also will not refresh the page,

As for the low, low, is a kind of personal feeling, this is not a technology problem, now has a large background system, still use cgi - bin

I think the choice of my hopes on the framework, it is very difficult to write good programs, specific problem specific solution, the abstracted problems often encountered, written reusable code, this adds up to write good programs,

CodePudding user response:

1. The asp.net MVC is the mainstream, the.net core is a trend,
2. Vue etc. More and more popular, you can try,
3. HTML (ajax) + web API (interface) are also popular,

CodePudding user response:

The.net MVC (core is not the core with you)

CodePudding user response:

MVC is a kind of development mode and the design idea, just like you said the WPF MMVM, but Microsoft do it better, especially the VS IDE collocation, more suitable for Microsoft programmers use,

HTML bloated problem has nothing to do with what use development, as a moderator said above, the industry division of labor is more and more refined, the so-called there are specializing in, what kind of development mode can solve the problem of what you said do not refresh the page,

From the perspective of Microsoft technology update iteration, personal or recommended. The.net MVC,