Why? Because almost all those features and shortcuts you know and love about Eclipse don’t work when writing Apex. My first tip to working with the plugin is for those who love and always use the Eclipse IDE for Java (please skip to the next paragraph if this doesn’t apply to you): pretend you aren’t really in Eclipse when coding in Apex. Note: For those who are unfamiliar with the IDE, please refer to this website for a general overview.ĭo you wish to wander into the world of Salesforce development, but don’t quite know how to manage the IDE? Struggling to get the IDE installed on your computer? You’ve wandered to the right place–I have some tips that may help you get started. If you have an account executive, consider contacting them to be put on a beta or pilot list.Tips & Tricks: The IDE in Eclipse for Windows 7

There's absolutely no way to get your hands on this today, that I'm aware of. Since I haven't seen it in any release notes, I'm under the assumption it's still some ways out, perhaps Winter 16 or beyond. However, all we have to work off of for now is hearsay and speculation until the details are finalized. I sincerely hope that's not the case, since developers like me would not have access to such a cool feature. It was stated that, at that time, they were considering that this feature only be enabled in Sandboxes, not Developer accounts or production, and the asking price they were considering was some fraction of a full sandbox. They also noted some caveats, such as the fact that breakpoints applied to all users, thus the need for developers and testers to keep out of each other's way, plus records that are involved remain locked for as long as the debugging session was active (so, perhaps some governor limits involved, in case you leave the session open over lunch).įinally, at the time of presentation, the feature wasn't going to be free for all, but pay to play. It included the ability to use multiple breakpoints, and it was suggested we would have the usual debugger commands, including Step Into, Step Over, and Stop (killing the current transaction). A few months ago, a local developer demonstrated this feature on a development stack running on a Mac (they were accessing Salesforce on In the demonstration, they set breakpoints in the IDE, triggered a request in the browser, and showed us how we could see the current stack, memory variables, etc. The debugger is a new feature coming down the pipes.

How to use eclipse force.com ide