Apex Code Development You need to sign in to do that
Don't have an account?
Using VS Code and connecting to Salesforce (replacing the MM layer)
While MavensMate is riding off into the sunset, it's going to remain relevant for a bit. That said, what's The Thing to use moving forward to connect VS Code, Atom, or Sublime to the Salesforce backend?
Thanks,
Steve
Thanks,
Steve
1) All About Salesforce Extensions for VS Code:
https://developer.salesforce.com/blogs/2018/02/salesforce-extensions-vs-code.html
The big problem is the migation to Salesforce DX tools (Scratch Org/Github/CLI) at the same time of using VS Code instead of MavensMate.
That is the new "official" development environment of Salesforce. I learned that during a Lex Tour in Paris from Philippe Ozil directly who only works now with SF DX and VS Code (he has given us a demonstration during the last Lightning Now Tour).
https://developer.salesforce.com/blogs/2018/02/getting-started-salesforce-dx-part-1-5.html
2) Migrating Existing Projects to Salesforce DX: By Christophe Coenraets (July 31, 2017)
Are you ready to move to Salesforce DX, but your source code is currently in a Developer Edition (DE) or Sandbox org?
In this blog post, I describe the easy steps to convert existing source code to a Salesforce DX project.
https://developer.salesforce.com/blogs/developer-relations/2017/07/migrating-existing-projects-salesforce-dx.html
3) Get Started with Salesforce DX: https://developer.salesforce.com/promotions/orgs/dx-signup
For the users of free developer orgs.
4) Scratch Orgs: The scratch org is a source-driven and disposable deployment of Salesforce code and metadata. A scratch org is fully configurable, allowing developers to emulate different Salesforce editions with different features and preferences. You can share the scratch org configuration file with other team members, so you all have the same basic org in which to do your development.
https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_scratch_orgs.htm
5) All the other tools including Eclipse Force.com IDE 2 will be deprecated soon.
I didn't have much experience with Salesforce DX either.
Migrating Existing Projects to Salesforce DX: the easy steps to convert existing source code to a Salesforce DX project ... but still complicated compared with MavensMate and its only needed credentials. GUI tools will simplified these steps probably direcly integrated in VS Code?
Salesforce Tools and Toolkits (official list):
UPDATED June 2018
Development Tools
1) Developer Edition Environment: This online environment lets you instantly start developing and testing your software-as-a-service application.
2) Scratch Orgs: The scratch org is a source-driven and disposable deployment of Salesforce code and metadata. A scratch org is fully configurable, allowing developers to emulate different Salesforce editions with different features and preferences. And you can share the scratch org configuration file with other team members, so you all have the same basic org in which to do your development.
3) Salesforce Extensions for VS Code: The Salesforce extensions for Visual Studio Code are a set of enhancements for custom development on the Salesforce Platform. Together, these extensions enable you and your team to use the VS Code IDE with Salesforce to deliver continuously.
4) Developer Console: The Developer Console is accessible from within your Salesforce organization, and provides a collection of tools you can use to create, edit, debug and test applications.
https://developer.salesforce.com/page/Tools
All the other tools including Eclipse Force.com IDE 2 have disappeared.
So - do the Salesforce Extensions for VS Code require that you use DX? As a consultant who's in LOTS of orgs, I need to be super flexible and need a solution that supports teams who've not yet switched over.
Thanks,
1) By the way, there is a big error here: https://developer.salesforce.com/page/Tools
Force.com IDE: This powerful Chrome extension lets you inspect and optimize Lightning Components by giving you access to a wealth of data about your running applications and components [ Chrome or perhaps ... Eclipse because it is still a link for Eclipse Force IDE but they don't want Eclipse anymore so now it became Chrome? ]
... that shows how little recognition they give to the developers using Eclipse IDE (one of the rare official Salesforce tools for developer until recently).
Last release Note : Winter ’17 (Force.com IDE v38.0) contains the following updates:
https://developer.salesforce.com/docs/atlas.en-us.eclipse.meta/eclipse/ide_release_notes.htm
https://resources.docs.salesforce.com/214/latest/en-us/sfdc/pdf/eclipse.pdf
... proof that there is no update the last year at least for the Eclipe IDE.
2) There are many videos and tutorials with Salesforce under GitHub and Scratch Orgs.
What Is Continuous Integration?
2.1) Continuous integration (CI) is a software development best practice. When using CI, all code that development teams produce is merged into a central repository, where an automated build can validate it. This practice helps development teams detect problems, identify bugs, and fix those problems and bugs before releasing changes to their customers.
For this module, we decided to take advantage of two cloud-based solutions:
- GitHub, a version control system (VCS), for our central repository
- Travis CI, which works well with GitHub (or Jenkins)
https://trailhead.salesforce.com/fr/modules/sfdx_travis_ci2.2) Salesforce: CONTINUOUS INTEGRATION AND CONTINUOUS DELIVERY WITH SALESFORCE DX
Josh Kaplan, Sr. Director, Product Management
http://salesforce.vidyard.com/watch/H3GHcWvD91oxcKeDtFksuN
Great video but ... he used Force.com IDE under Eclipse (obsolete)
We need this kind of video with MS VSCode. The American videos are often done in a handy way but it is missing.
3) Migrate or Import Existing Source: (horribly complicated, not practical at all)
Eleven steps and each step has a dozen of command lines (and they say that we must be fond of the return of these commande lines)
https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_intro_existing_app.htm
MavensMate, just the credentials but you don't have the VCS (version control system).
https://www.youtube.com/watch?v=Ez5ITRJBres
Salesforce Developers - 16 nov. 2017
Are you an Eclipse user? Curious about our new extension for Visual Studio Code? Worried about learning a new tool? Join us as we highlight the differences and give recommendations for long-time Eclipse users. We'll explain how to easily adapt your development workflows to get the best experience right from the beginning.
... and become an expert of the command lines just called from VS code.
2) From Change Sets to Salesforce DX: The Evolution of Collaboration
https://www.youtube.com/watch?v=FUFkbr9uueU
... they should write: "From simple free change sets to expensive licenses of Auto Rabit."
https://www.autorabit.com/autorabit-for-salesforce/
There are handy tools like the former obsolete free Eclipse Force.com IDE but you must pay.
Otherwise, you can just use the commande lines of SFDX.
List of IDE available for Salesforce coding (obsolete, 2015) but still interesting
https://www.jitendrazaa.com/blog/salesforce/list-of-ide-available-for-salesforce-coding/
His choice and I also use it very often:
Developer Console: This is currently my choice of development IDE and currently recommended and supported by Salesforce. There are lots of capability to fall in love with this editor and most important is Performance profiling, Checkpoints, Query execution plan, Log files and many more to count.
IntelliJ IDEA is often considered as the best Java IDE: Illuminated Cloud is a powerful Salesforce development tool hosted within JetBrains IntelliJ IDEA. Support for both traditional and Salesforce DX projects: https://plugins.jetbrains.com/plugin/7831-illuminated-cloud
... project very active but the annual subscription price for a Commercial license of Illuminated Cloud is $125 USD ... each
( Force.com IDE was $0 USD )
VIDEO: What's Next for Illuminated Cloud? Overview of 2.0 and SFDX Support with Scott Wells
https://www.youtube.com/watch?v=wEQvqb3d774
Automatic creation of a scratch org at the click of a button :
Scott Wells (Austin, Texas) has created "alone" the best IDE extension for Salesforce for both traditional and Salesforce DX.
Why Salesforce has never done that? That was the former Force.com IDE 2 which has completely disappeared.
https://github.com/forcedotcom/salesforcedx-vscode/wiki/Develop-Against-Any-Org-in-Visual-Studio-Code
Setup was not terribly smooth: I had to substitue the command line below for the SFDX: Authorize on Org command described in the instructions.
Many developers abandoned the use of Force.com IDE (Eclipse) as soon as they have tried MavensMate under Sublime (very fast, handly and simple).
But with VS Code, it is not handy at all and moreover, that will be the slowest development tool for Salesforce that we have never seen.before.
Salesforce DX Modular Development with Zayne Turner: https://www.youtube.com/watch?v=Y7QsVQLkaWM
https://developer.salesforce.com/blogs/author/zayne
I have just been watching this video (Salesforce DX Modular Development) and she quickly abandonned the integrated command lines in VS Code because she prefers to write all the command lines completely in a ... console.
The reason: she wants to learn the numerous (complicated) command lines of SFDX and probably also because you are never sure of what you are doing exactly when you launched the "integrated" command lines in VS Code. Zayne Turner is an expert of Salesforce DX.
At the end of the video, someone asked a question about the price he must pay now for his new developer environment (expensive)..
VS Code is just great ... for the syntax highlighting finally.
Salesforce Developers: 17 oct. 2018: Knowing how an IDE works can drastically simplify a developer's day-to-day job. In this webinar, Zayne and René dive into Visual Studio Code. No matter if you're a Salesforce Developer familiar with the good old Force.com IDE, now looking to move to VS code or if you’re brand new to developing on the Salesforce Platform. This webinar will bring you up to high-productivity!
Table of Contents:
03:48 - Marker
03:58 - What is VS Code?
07:23 - Demo
31:00 - Trail!
32:28 - Q&A
GitLab is free (that seems)?
VS Code has now great tools for the debugging especially but the main problem was the slowness.
Did you notice this slowness of VS Code? or it is quite the same than the other tools you have used before?
Regards
Alain
We are using GitLab mostly for the CI / CD features (Continuous Integration/Delivery). I believe both GitLab and GitHub are paid.
I am very interested in the Apex debugging with VS Code. I have not found any Apex debugging in VS Code without paying for the license from Salesforce. I opened this question here (https://success.salesforce.com/answers?id=9063A000000t4ICQAY), but didn't get any information on it. How are you doing Apex debugging in VS Code???
I have noticed slowness in VS Code only when doing a deploy to source org using a sandbox. Mine takes 30 seconds or so. We are still new to Salesforce DX and right now are trying to get it working with sandboxes while we quickly try to get up to speed on scratch orgs, while we also produce deliverables for the customer. It keeps things interesting.
Denise
Evan McDaniel said 90 seconds at first above (far too slow) but we really have no choice for free tools anyway.
Spring 19: Revolution with the new "Lightning web components".
- Enable Dev Hub in a Developer Edition pre-release org:
Quick Start: Lightning Web Components: Set up your developer environment and create your first Lightning web component.If you don’t have a pre-release org, sign up for a pre-release Developer Edition at https://www.salesforce.com/form/signup/prerelease-spring19/
https://trailhead.salesforce.com/fr/content/learn/projects/quick-start-lightning-web-components?trail_id=force_com_dev_intermediate
- Introducing Lightning Web Components By Christophe Coenraets December 13, 2018
Topics: Lightning Web Components is a new programming model for building Lightning components. It leverages the web standards breakthroughs of the last five years, can coexist and interoperate with the original Aura programming model, and delivers unparalleled performance.https://developer.salesforce.com/blogs/2018/12/introducing-lightning-web-components.html
https://developer.salesforce.com/page/Tools
... still many broken links. No more Eclipse IDE but VS Code only. Very poor official page for the tools.
Example of link:: Salesforce Reports for Excel (Pilot) Pilot of ... 2007.
End of Support for Excel Add-In from Connect for Office in March 4 2017
https://help.salesforce.com/articleView?id=000240053&type=1&language=en_US
A more interesting page by a former Salesforce employee: awesome-salesforce: https://github.com/mailtoharshit/awesome-salesforce
Local Development for Lightning Web Components: 25 june 2019
Historically, building components in Salesforce has relied upon a connection to an org. With Lightning Web Components, Salesforce had moved to an open, standards-based approach to development that makes building components locally not only possible, but an excellent experience for rapid iteration and release. In this session, we'll walk you through local development for LWC, introducing you to this new capability for previewing and rendering components from localhost. You'll see live demos and code walkthroughs, and walk away ready to spin up VS Code and enjoy an improved developer experience with rich error handling, local rendering, @wire, and much more!
https://www.youtube.com/watch?v=nygnbZj4EXs
VS Code will be not the slowest development tool for Salesforce that we have never seen before with this new environment.
https://www.metarocket.io