Brief analysis of Standard Controllers for Visualforce page
Extra data about utilizing standard controllers:
Standard Controllers:
A Visualforce controller is an arrangement of directions that indicate what happens when a client cooperates with the parts determined in related Visualforce markup, for example, when a client clicks a catch or connection. Controllers likewise give access to the information that thought to be shown in a page, and can alter segment conduct.
Extra data about utilizing standard controllers:
· Partner a Standard Controller with a Visualforce Page
· Getting to Data with a Standard Controller
· Utilizing Standard Controller Actions
· Approval Rules and Standard Controllers
· Styling Pages that Use Standard Controllers
· Checking for Object Accessibility
· Custom Controllers and Controller Extensions
Create & Use Custom Controllers
Prologue to Custom Controllers:
Custom controllers contain custom rationale and information control that can be utilized by a Visualforce page. How Visualforce bolsters the Model– View– Controller (MVC) plan design for building web applications. Controllers regularly recover the information to be shown in a Visualforce page, and contain code that executes in light of page activities, for example, a catch being clicked. When you utilize the standard controller, a lot of, well, standard usefulness is given to you by the stage.
Make a Visualforce Page that Uses a Custom Controller:
By or take a reference the name of the controller class
<apex:page> controller Attribute
At the point when your page utilizes a custom controller, you can't utilize a standard controller.
• Open the Developer Console and snap File | New | Visualforce Page to make another Visualforce page. Enter Contacts List Controller for the page name.
• In the editorial manager, supplant any markup with the accompanying.
<apex:page controller="ContactsListController">
<apex:form>
<apex:pageBlock title="Contacts List" id="contacts_list">
<!-- Contacts List goes here -->
</apex:pageBlock>
</apex:form>
</apex:page>