Play by Play: Battle of the Salesforce IDEs

In this course, you’ll dive into the almost endless choices of development environments that are offered by Salesforce and the community while exploring the benefits and limitations of each one.
Course info
Level
Beginner
Updated
Nov 20, 2017
Duration
2h 16m
Table of contents
Description
Course info
Level
Beginner
Updated
Nov 20, 2017
Duration
2h 16m
Description

Play by Play is a series in which top technologists work through a problem in real time, unrehearsed, and unscripted. In this course, Play by Play: Battle of the Salesforce IDEs, Robert Watson and Don Robins work their way through a number of the IDEs available for Salesforce Development. They will take you into a real-world development scenario and progress through The Developer Console, the Eclipse Force.com IDE, VSCode with MavensMate, Illuminated Cloud for IntelliJ, while discussing the pros and cons of each. By the end of this course, you’ll understand the benefits for many of the available IDEs and how to get started using them in your environment.

About the author
About the author

Don Robins is a well known Salesforce MVP, instructor, author, and speaker. A custom business application developer for more decades than he cares to admit, he focuses on Salesforce technical instruction and knowledge sharing.

More from the author
More courses by Don Robins
About the author

Robert has been a Salesforce developer for Salesforce ISV partners since 2012, and is currently a senior software developer at Full Circle Insights. As an engineer on the Salesforce platform, he has helped to design and implement complex and highly successful applications on the AppExchange that are pushing the boundaries of Salesforce development.

Section Introduction Transcripts
Section Introduction Transcripts

Course Overview
Welcome to this Salesforce Play by Play with Pluralsight. Salesforce Play by Play is an interactive series where we sit down with Salesforce experts such as MVPs, consultants, developers, and architects, to discuss common challenges faced every day by Salesforce customers. We'll be learning while discussing concepts and debating tradeoffs on various approaches to solving real-world problems. We learn by reviewing system configurations, or writing code, and then exploring the benefits of any particular solution. In this course, we challenge Robert Watson, senior software developer at Full Circle Insights to help us understand the many options that Salesforce developers have when choosing their IDE, or Integrated Development Environment. Robert walks us through some of the many options available, and we discuss some tradeoffs, along with pros and cons of each, using a real-world team development scenario. As we progress he demonstrates some common development tasks using several different IDEs, from the perspective of multiple team members, each with their own development styles and needs. Along the way we learn about how each of these IDEs with support working with an orgs meta data and code base stored in a source control repository. By the time we're done, you'll have a clear understanding of what your options are, and why you might choose one IDE over any other, based on your own specific needs. Whether you focus your development on Apex, Visualforce, or Lightning Components, come learn about your choices when selecting from available Salesforce IDEs. Please join us for the battle of the Salesforce IDEs, we hope you enjoy it!

Developer Console and Built-in Cloud-based Tools
So I've been doing all of this in the developer console. Let's see what that looks like. Alright, let's take a look. From my Salesforce org I can actually access the Developer Console right from Setup, and I'm just going to open it in a new tab, I'm going to Ctrl+Click on the link here. And so the nice thing we see here, the developer console is your IDE baked right into Salesforce. So, the URL I'm at right now is you know, I'm pointed directly to the developer console right in my sandbox. And we'll see here, I've been working obviously on the Lightning components, so I already have all of these files already open, I have my Lightning component bundle, and then I can navigate between the different resources in that bundle, the COMPONENT, the CONTROLLER, the HELPER. It's nice here because it's a Lightning component I can even navigate over here on the right as well back and forth. And I'm noticing that the bundle navigation on the right, you're only working with three resources, you potentially have eight resources to work with in a Lightning bundle, and there is definitely a color code difference, it's saying there is some content there, so that's nice, it gives you a nice visual, visual cue.

Eclipse Force.com IDE and Source Control Integration
So what we're going to explore first is the Eclipse Force. com IDE. So what are we going to see? Well, first, before we can start using Eclipse, what we want to do first is pull down the Git repository onto our local machine. So we want to focus on where the code is being stored from all three of the team members where the source of truth is and how to integrate, get into your desktop environment… Right. So our goal right now is to get all of our team member's code, get it onto our local machine, set up our project in Eclipse, pull down everything that we've worked on in our Salesforce org onto our local machine. And then, we'll also be able to then deploy and save all of our coworker's code to our Salesforce org. Got it. So we're doing a merge, basically doing a pull, and this is from the context of Dan, right? He's the developer, he's been working the developer console, Dan the developer console guy, and he's now moving to this desktop environment and he's going to be using Eclipse and the Force. com IDE, and he's got to integrate this with Git, he's got to pull the code in. Okay, great. So it can be a little bit complicated, but once you have the project set up then you won't need a, it becomes less complicated. Sure, the more you do, the easier it gets.