ASP.NET Confusion - Server Controls

I read the information in this question: Manages standard HTML , but I'm still pretty confused.

The situation I asked to do a web project, where I created a wizard. When I finished the project, everyone asked why I used <asp:Wizard...>. I thought that this is what they asked for, but apparently not, so after that it occurred to me that the server controls are just prototypes.

However, in the next project, I fulfilled my database queries using C # code and uploaded the results via html. Then I was asked why I did not use gridview and dataset.

Does anyone have a list of pros and cons, why do they prefer to use certain html controls for certain server controls, and why? I’m probably looking for a list ... which server controls are suitable and why?

EDIT: I think this question is open, so I will clarify a few more specific questions ...

  • Is it possible to use very simple controls such as asp: Label, or do it just end up wasting space? It seems like it would be hard to access html in code located differently.

  • Are there a few controls that should never be used?

  • Does anyone have a good resource that will show me the pros and cons of each control?

+3
source share
2

ViewState,

WinForms -. , Server Controls, . , - WebForms , .

Server Controls , , ViewState , . ViewState , .

ViewState, , , HTML.

HTML -, , -. , JavaScript framework.

+3
  • , asp: Label ? html .

, . , .

  1. , ?

( ) . Wizard, , , ( , ). , .

  1. - , ?

, . Repeater GridView, , .

, . , MVC . . AJAX, .NET JQuery , AJAX (UpdatePanels ), JSON - .

+1

Source: https://habr.com/ru/post/1740842/


All Articles