The next webform we're going to learn will integrate what we're learning now.
In contrast to WinForm, we see
Winform
Interface End service logic end data Access end
form Controls C # code object-oriented ADO
WebForm
Interface End service logic end data Access end
Html+css+js C # code object-oriented ADO
---------------------------------------------------
First WebForm need to remotely access the database, not as we winform to access the local database, so
The WebForm process is:
Customer Interface →iis Server →.net framwork→sqlserver→.net framwork (data processing) →IIS server
→ Customer Interface
The client (Winform) processes the data in the customer's computer
While web-side processing data is on the IIS server
-----------------------------------------------------------
I. Start-up status differences:
1. Start running (slow execution)
2. Right-click on the HTML code and view it in the browser
Two. How the event delegate is written
Now do not need to double-click Write, but need delegate
Delegate notation for events: + = Tab tab
Three. No State of HTTP
Everything that needs to be loaded at startup is written in here.
if (IsPostBack = = False)
{}
* Event delegate cannot be written inside
Four. Database connection
There's no big difference, there's no namespace.
Five. Use pure CSS and JS to create styles and effects for any effect or content on the interface.
1013 Meet WebForm