Announcing the November Twin Cities Salesforce.com Developer User Group meeting!

Hello everyone!  It's that time again!

What are we doing?

Developer 101:  How to write basic triggers, classes, and Visualforce pages.

We will be going through some basic examples of writing APEX and Visualforce, best practices, and how to write good test classes for deployment to production.

What is "HOT"?  HOT = "Hands on Training".  Bring your laptop and be ready to code!  All experience levels are welcome.  

Topics Covered:

Declarative vs. Programmatic - good developer practice Order of Execution Writing your first trigger Scope (before, after) Actions (insert, update, delete, undelete) Test Classes Bulkification Writing your first class Standard Controller Custom Controller Standard Set Controller GET / SET Methods Test Classes Bulkification Visualforce Pages Standard Controller Custom Controller <apex:...> tags Handling Errors  

When and where are we doing it?

November 7th, 2012 3pm-6pm

Location:  TBD in the Eagan / Mendota Heights area

** We will have water and snacks available

What should I bring and what tools do I need to have?

You should absolutely bring your laptop - this will be a live hands-on-training session.  WiFi will be provided.

If you are new to APEX development, you can either load the Force.com IDE prior to the meeting or choose to use the Developer Console.  I will have both running for examples, but will be working primarily out of Developer Console.

You also should create your own Salesforce Developer Edition account if you don't already have one prior to the meeting.  A DE comes loaded with sample data that we will be referencing during the session.  To sign up for a Developer Edition account, visit http://developer.force.com and click the "Join Now" link at the top.

Due to this meeting being hands-on, space is limited; RSVP today!  See you all in November!

Questions?  Hit me on email or Twitter.  Thanks!

====--------
Andy Boettcher (@andyboettcher)
Twin Cities Salesforce.com Developer Group (@tc_dug)