Learning force com application development

Development tools are the tools that are used to develop the application, including some portion of declarative (point-click) development (creating objects and fields using metadata) and programming development (Apex classes, triggers, and Visualforce pages). The development tools are as follows:

• Force.com IDE : The Force.com IDE is an open source (you can download the source from https://github.com/forcedotcom/idecore ) Eclipse-based tool, which can be used to create, modify, and deploy the Force.com application from a local computer. It provides a full-featured, collaborative development environment for coding, compiling and testing, and version controlling. The major features of the Force.com IDE are as follows:

• Writing and managing Apex classes and triggers.
• Unit tests can be executed with the Apex Test Runner and can provide the code coverage report.
• Locating the syntax errors while you are writing the code and providing error messages and debugging output.
• Creating, modifying, and downloading all the metadata components available in the metadata API.
• Creating and editing Visualforce pages and Visualforce components.
• The schema explorer allows you to execute SOAL queries and you can see all the standard and custom objects with their fields. You just need to pick particular fields to generate the SOAL query.
• It deploys application components to the production organization or any other organization with the Deploy to Server wizard.
• By integrating the Eclipse-enabled version control system, you can develop, test, and deploy your application in a collaborative environment.
• The Force.com IDE can detect and resolve the conflicting changes between online and local versions of the application.

• To prepare a test environment with enormous volumes of setup changes in a short time.
• Typically, in a development process, we maintain iterative development; testing phases and final release will be deployed to the production organization. Using the Force.com migration tool, you can maintain a scripted retrieval and deployment process, which is more efficient. More details about the migration tool can be found at https://developer.salesforce.com/page/Force.com_Migration_Tool .

• Create Apex classes, triggers, Visualforce pages, Visualforce components, and static resources.
• Edit Apex classes, triggers, Visualforce pages, and Visualforce components. There is an in-built code editor in the developer console.
• Open Apex classes, triggers, Visualforce pages, objects, Visualforce components, packages, and static resources.
• Debugging and troubleshooting through viewing logs, set and view checkpoints in Apex code.
• Executing the anonymous code.
• Testing and validating the performance of the code by testing the Apex code and inspecting logs for performance issues.
• Executing SOQL and SOSL queries via the in-built query editor and viewing the query results.
• For more details visit https://help.salesforce.com/apex/HTViewHelpDoc?id=code_system_log.htm .

Tip

The Force.com IDE, the Force.com migration tool, and the developer console are Salesforce supported tools.

• Bulk API
• Streaming API
• Rest API
• Apex API
• Metadata API