Mixing
VS Code for Salesforce - can we start from the beginning?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
5
down vote
favorite
I get frustrated trying to get this VS Code thing off the ground. It is like someone says "Fly to Dreamforce" and I'm still trying to figure out what an airplane is.
I've got VS Code installed. JDK installed. Salesforce CLI installed. Salesforce Extensions installed. I got my fingers crossed. It doesn't work for me - it doesn't do anything. I try "Create Project with Manifest" and it just sits there - nothing happens.
Anyone know of a place to go to that takes it from the beginning, from kindergarden, and steps you through the process rather than starting at 10th grade?
vs-code
asked 2 hours ago
Dean Wooldridge
511
add a comment |Â
up vote
5
down vote
favorite
I get frustrated trying to get this VS Code thing off the ground. It is like someone says "Fly to Dreamforce" and I'm still trying to figure out what an airplane is.
I've got VS Code installed. JDK installed. Salesforce CLI installed. Salesforce Extensions installed. I got my fingers crossed. It doesn't work for me - it doesn't do anything. I try "Create Project with Manifest" and it just sits there - nothing happens.
Anyone know of a place to go to that takes it from the beginning, from kindergarden, and steps you through the process rather than starting at 10th grade?
vs-code
asked 2 hours ago
Dean Wooldridge
511
1
Do you want to use it with DX or directly with a regular sandbox?
– David Cheng
37 mins ago
add a comment |Â
up vote
5
down vote
favorite
up vote
5
down vote
favorite
I get frustrated trying to get this VS Code thing off the ground. It is like someone says "Fly to Dreamforce" and I'm still trying to figure out what an airplane is.
I've got VS Code installed. JDK installed. Salesforce CLI installed. Salesforce Extensions installed. I got my fingers crossed. It doesn't work for me - it doesn't do anything. I try "Create Project with Manifest" and it just sits there - nothing happens.
Anyone know of a place to go to that takes it from the beginning, from kindergarden, and steps you through the process rather than starting at 10th grade?
vs-code
asked 2 hours ago
Dean Wooldridge
511
I get frustrated trying to get this VS Code thing off the ground. It is like someone says "Fly to Dreamforce" and I'm still trying to figure out what an airplane is.
I've got VS Code installed. JDK installed. Salesforce CLI installed. Salesforce Extensions installed. I got my fingers crossed. It doesn't work for me - it doesn't do anything. I try "Create Project with Manifest" and it just sits there - nothing happens.
Anyone know of a place to go to that takes it from the beginning, from kindergarden, and steps you through the process rather than starting at 10th grade?
vs-code
vs-code
asked 2 hours ago
Dean Wooldridge
511
asked 2 hours ago
Dean Wooldridge
511
asked 2 hours ago
Dean Wooldridge
511
asked 2 hours ago
Dean Wooldridge
511
asked 2 hours ago
Dean Wooldridge
511
511
1
Do you want to use it with DX or directly with a regular sandbox?
– David Cheng
37 mins ago
add a comment |Â
1
Do you want to use it with DX or directly with a regular sandbox?
– David Cheng
37 mins ago
1
1
Do you want to use it with DX or directly with a regular sandbox?
– David Cheng
37 mins ago
Do you want to use it with DX or directly with a regular sandbox?
– David Cheng
37 mins ago
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
3
down vote
There's a handy video you can watch on Getting Started in VS Code with Salesforce DX.
Getting Started
First things first: it's important to note that VS Code places extension prompts at the very top of the screen, instead of the more usual center of the screen. You'll need to pay attention to these dialogs, which are not immediately obvious. Once you get used to this, you'll find that Code is not that hard to use, it's just different than most other IDEs.
To make a new DX project, choose the Create Project from Manifest command, and you'll see a small text area at the top that says "Enter project name (Press 'Enter' to confirm or 'Esc' to cancel)." Type in the name you'd like to use for your project (it can be any reasonable text).
Next, you'll get a Folder Selection dialog. Choose a place you'd like to save your project. It's helpful if you've already created a workspace folder to store all your projects in, such as c:usersyour.nameworkspace. Once you select the folder, you'll see a brief progress dialog, after which your project will be ready.
Once you do this, you'll probably want to Authorize a Dev Hub org. There are steps you must follow to enable Dev Hub functionality before you can use this command. The Dev Hub can be a Developer Org or your Production Org. This is optional, but if you do not do this, you won't be able to create scratch orgs. If you're just using a sandbox or developer edition, you can choose Authorize an Org instead.
Again, pay attention to the dialog at the top of the screen. You'll want to enter an alias (strongly recommended), which is simply a nickname for the org you're authorizing. After that, you'll be prompted to log in through your default browser. Once logged in, you can go back to Code.
If you're using Scratch Orgs, you can create a new Scratch Org, which will take a preferences file (one was created in your project automatically) and an alias. After about a minute, you'll have a new, empty org. Everything else from there is just development; you can use the DX commands to create new classes, pages, components, etc, or you can manually create the source files if you prefer.
Or, you can log in to the scratch org, make changes there, and use SFDX to pull changes down to your computer. Choose whichever works best for you. You'll notice when you create a scratch org that you have no username or password; this is fine by default, as you can just choose "Open Default Org" to go to the scratch org you created. Note that not all DX commands and options are exposed, so you might need to use the Terminal from time to time.
To do this, just click on the Terminal tab, and you can use the sfdx command with all its options. You can check the Salesforce CLI Command Reference for a full list of commands and options available. You'll also want to read more about the configuration options for your scratch orgs and other settings, but this should at least help you get started.
Also, feel free to Get Started with Salesforce DX over on Salesforce Trailhead for more DX basics. These are not VS Code specific, but will help you understand the intended development cycle.
edited 1 hour ago
Raul
11.3k21738
answered 1 hour ago
sfdcfox
237k10181400
@Raul Thank you for fixing the typo! I somehow missed this during my proofreading.
– sfdcfox
1 hour ago
Nice answer, curious to know if it is only me or push to DX is very slow?
– Raul
1 hour ago
1
@Raul It depends on the number of files involved on your file system. It can take a few seconds to a few minutes. It's definitely noticeably slower than Force.com IDE is/was, but it's also a lot better at detecting many changes. Just like building a repo, the first push is always the longest; subsequent pushes should be much faster, as it checks for local disk diff changes, but this still takes more time than other IDEs that just deploy the changed file directly.
– sfdcfox
1 hour ago
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
There's a handy video you can watch on Getting Started in VS Code with Salesforce DX.
Getting Started
First things first: it's important to note that VS Code places extension prompts at the very top of the screen, instead of the more usual center of the screen. You'll need to pay attention to these dialogs, which are not immediately obvious. Once you get used to this, you'll find that Code is not that hard to use, it's just different than most other IDEs.
To make a new DX project, choose the Create Project from Manifest command, and you'll see a small text area at the top that says "Enter project name (Press 'Enter' to confirm or 'Esc' to cancel)." Type in the name you'd like to use for your project (it can be any reasonable text).
Next, you'll get a Folder Selection dialog. Choose a place you'd like to save your project. It's helpful if you've already created a workspace folder to store all your projects in, such as c:usersyour.nameworkspace. Once you select the folder, you'll see a brief progress dialog, after which your project will be ready.
Once you do this, you'll probably want to Authorize a Dev Hub org. There are steps you must follow to enable Dev Hub functionality before you can use this command. The Dev Hub can be a Developer Org or your Production Org. This is optional, but if you do not do this, you won't be able to create scratch orgs. If you're just using a sandbox or developer edition, you can choose Authorize an Org instead.
Again, pay attention to the dialog at the top of the screen. You'll want to enter an alias (strongly recommended), which is simply a nickname for the org you're authorizing. After that, you'll be prompted to log in through your default browser. Once logged in, you can go back to Code.
If you're using Scratch Orgs, you can create a new Scratch Org, which will take a preferences file (one was created in your project automatically) and an alias. After about a minute, you'll have a new, empty org. Everything else from there is just development; you can use the DX commands to create new classes, pages, components, etc, or you can manually create the source files if you prefer.
Or, you can log in to the scratch org, make changes there, and use SFDX to pull changes down to your computer. Choose whichever works best for you. You'll notice when you create a scratch org that you have no username or password; this is fine by default, as you can just choose "Open Default Org" to go to the scratch org you created. Note that not all DX commands and options are exposed, so you might need to use the Terminal from time to time.
To do this, just click on the Terminal tab, and you can use the sfdx command with all its options. You can check the Salesforce CLI Command Reference for a full list of commands and options available. You'll also want to read more about the configuration options for your scratch orgs and other settings, but this should at least help you get started.
Also, feel free to Get Started with Salesforce DX over on Salesforce Trailhead for more DX basics. These are not VS Code specific, but will help you understand the intended development cycle.
edited 1 hour ago
Raul
11.3k21738
answered 1 hour ago
sfdcfox
237k10181400
@Raul Thank you for fixing the typo! I somehow missed this during my proofreading.
– sfdcfox
1 hour ago
Nice answer, curious to know if it is only me or push to DX is very slow?
– Raul
1 hour ago
1
@Raul It depends on the number of files involved on your file system. It can take a few seconds to a few minutes. It's definitely noticeably slower than Force.com IDE is/was, but it's also a lot better at detecting many changes. Just like building a repo, the first push is always the longest; subsequent pushes should be much faster, as it checks for local disk diff changes, but this still takes more time than other IDEs that just deploy the changed file directly.
– sfdcfox
1 hour ago
add a comment |Â
up vote
3
down vote
There's a handy video you can watch on Getting Started in VS Code with Salesforce DX.
Getting Started
First things first: it's important to note that VS Code places extension prompts at the very top of the screen, instead of the more usual center of the screen. You'll need to pay attention to these dialogs, which are not immediately obvious. Once you get used to this, you'll find that Code is not that hard to use, it's just different than most other IDEs.
To make a new DX project, choose the Create Project from Manifest command, and you'll see a small text area at the top that says "Enter project name (Press 'Enter' to confirm or 'Esc' to cancel)." Type in the name you'd like to use for your project (it can be any reasonable text).
Next, you'll get a Folder Selection dialog. Choose a place you'd like to save your project. It's helpful if you've already created a workspace folder to store all your projects in, such as c:usersyour.nameworkspace. Once you select the folder, you'll see a brief progress dialog, after which your project will be ready.
Once you do this, you'll probably want to Authorize a Dev Hub org. There are steps you must follow to enable Dev Hub functionality before you can use this command. The Dev Hub can be a Developer Org or your Production Org. This is optional, but if you do not do this, you won't be able to create scratch orgs. If you're just using a sandbox or developer edition, you can choose Authorize an Org instead.
Again, pay attention to the dialog at the top of the screen. You'll want to enter an alias (strongly recommended), which is simply a nickname for the org you're authorizing. After that, you'll be prompted to log in through your default browser. Once logged in, you can go back to Code.
If you're using Scratch Orgs, you can create a new Scratch Org, which will take a preferences file (one was created in your project automatically) and an alias. After about a minute, you'll have a new, empty org. Everything else from there is just development; you can use the DX commands to create new classes, pages, components, etc, or you can manually create the source files if you prefer.
Or, you can log in to the scratch org, make changes there, and use SFDX to pull changes down to your computer. Choose whichever works best for you. You'll notice when you create a scratch org that you have no username or password; this is fine by default, as you can just choose "Open Default Org" to go to the scratch org you created. Note that not all DX commands and options are exposed, so you might need to use the Terminal from time to time.
To do this, just click on the Terminal tab, and you can use the sfdx command with all its options. You can check the Salesforce CLI Command Reference for a full list of commands and options available. You'll also want to read more about the configuration options for your scratch orgs and other settings, but this should at least help you get started.
Also, feel free to Get Started with Salesforce DX over on Salesforce Trailhead for more DX basics. These are not VS Code specific, but will help you understand the intended development cycle.
edited 1 hour ago
Raul
11.3k21738
answered 1 hour ago
sfdcfox
237k10181400
@Raul Thank you for fixing the typo! I somehow missed this during my proofreading.
– sfdcfox
1 hour ago
Nice answer, curious to know if it is only me or push to DX is very slow?
– Raul
1 hour ago
1
@Raul It depends on the number of files involved on your file system. It can take a few seconds to a few minutes. It's definitely noticeably slower than Force.com IDE is/was, but it's also a lot better at detecting many changes. Just like building a repo, the first push is always the longest; subsequent pushes should be much faster, as it checks for local disk diff changes, but this still takes more time than other IDEs that just deploy the changed file directly.
– sfdcfox
1 hour ago
add a comment |Â
up vote
3
down vote
up vote
3
down vote
There's a handy video you can watch on Getting Started in VS Code with Salesforce DX.
Getting Started
First things first: it's important to note that VS Code places extension prompts at the very top of the screen, instead of the more usual center of the screen. You'll need to pay attention to these dialogs, which are not immediately obvious. Once you get used to this, you'll find that Code is not that hard to use, it's just different than most other IDEs.
To make a new DX project, choose the Create Project from Manifest command, and you'll see a small text area at the top that says "Enter project name (Press 'Enter' to confirm or 'Esc' to cancel)." Type in the name you'd like to use for your project (it can be any reasonable text).
Next, you'll get a Folder Selection dialog. Choose a place you'd like to save your project. It's helpful if you've already created a workspace folder to store all your projects in, such as c:usersyour.nameworkspace. Once you select the folder, you'll see a brief progress dialog, after which your project will be ready.
Once you do this, you'll probably want to Authorize a Dev Hub org. There are steps you must follow to enable Dev Hub functionality before you can use this command. The Dev Hub can be a Developer Org or your Production Org. This is optional, but if you do not do this, you won't be able to create scratch orgs. If you're just using a sandbox or developer edition, you can choose Authorize an Org instead.
Again, pay attention to the dialog at the top of the screen. You'll want to enter an alias (strongly recommended), which is simply a nickname for the org you're authorizing. After that, you'll be prompted to log in through your default browser. Once logged in, you can go back to Code.
If you're using Scratch Orgs, you can create a new Scratch Org, which will take a preferences file (one was created in your project automatically) and an alias. After about a minute, you'll have a new, empty org. Everything else from there is just development; you can use the DX commands to create new classes, pages, components, etc, or you can manually create the source files if you prefer.
Or, you can log in to the scratch org, make changes there, and use SFDX to pull changes down to your computer. Choose whichever works best for you. You'll notice when you create a scratch org that you have no username or password; this is fine by default, as you can just choose "Open Default Org" to go to the scratch org you created. Note that not all DX commands and options are exposed, so you might need to use the Terminal from time to time.
To do this, just click on the Terminal tab, and you can use the sfdx command with all its options. You can check the Salesforce CLI Command Reference for a full list of commands and options available. You'll also want to read more about the configuration options for your scratch orgs and other settings, but this should at least help you get started.
Also, feel free to Get Started with Salesforce DX over on Salesforce Trailhead for more DX basics. These are not VS Code specific, but will help you understand the intended development cycle.
edited 1 hour ago
Raul
11.3k21738
answered 1 hour ago
sfdcfox
237k10181400
There's a handy video you can watch on Getting Started in VS Code with Salesforce DX.
Getting Started
First things first: it's important to note that VS Code places extension prompts at the very top of the screen, instead of the more usual center of the screen. You'll need to pay attention to these dialogs, which are not immediately obvious. Once you get used to this, you'll find that Code is not that hard to use, it's just different than most other IDEs.
To make a new DX project, choose the Create Project from Manifest command, and you'll see a small text area at the top that says "Enter project name (Press 'Enter' to confirm or 'Esc' to cancel)." Type in the name you'd like to use for your project (it can be any reasonable text).
Next, you'll get a Folder Selection dialog. Choose a place you'd like to save your project. It's helpful if you've already created a workspace folder to store all your projects in, such as c:usersyour.nameworkspace. Once you select the folder, you'll see a brief progress dialog, after which your project will be ready.
Once you do this, you'll probably want to Authorize a Dev Hub org. There are steps you must follow to enable Dev Hub functionality before you can use this command. The Dev Hub can be a Developer Org or your Production Org. This is optional, but if you do not do this, you won't be able to create scratch orgs. If you're just using a sandbox or developer edition, you can choose Authorize an Org instead.
Again, pay attention to the dialog at the top of the screen. You'll want to enter an alias (strongly recommended), which is simply a nickname for the org you're authorizing. After that, you'll be prompted to log in through your default browser. Once logged in, you can go back to Code.
If you're using Scratch Orgs, you can create a new Scratch Org, which will take a preferences file (one was created in your project automatically) and an alias. After about a minute, you'll have a new, empty org. Everything else from there is just development; you can use the DX commands to create new classes, pages, components, etc, or you can manually create the source files if you prefer.
Or, you can log in to the scratch org, make changes there, and use SFDX to pull changes down to your computer. Choose whichever works best for you. You'll notice when you create a scratch org that you have no username or password; this is fine by default, as you can just choose "Open Default Org" to go to the scratch org you created. Note that not all DX commands and options are exposed, so you might need to use the Terminal from time to time.
To do this, just click on the Terminal tab, and you can use the sfdx command with all its options. You can check the Salesforce CLI Command Reference for a full list of commands and options available. You'll also want to read more about the configuration options for your scratch orgs and other settings, but this should at least help you get started.
Also, feel free to Get Started with Salesforce DX over on Salesforce Trailhead for more DX basics. These are not VS Code specific, but will help you understand the intended development cycle.
edited 1 hour ago
Raul
11.3k21738
answered 1 hour ago
sfdcfox
237k10181400
edited 1 hour ago
Raul
11.3k21738
edited 1 hour ago
Raul
11.3k21738
edited 1 hour ago
Raul
11.3k21738
11.3k21738
answered 1 hour ago
sfdcfox
237k10181400
answered 1 hour ago
sfdcfox
237k10181400
answered 1 hour ago
sfdcfox
237k10181400
237k10181400
@Raul Thank you for fixing the typo! I somehow missed this during my proofreading.
– sfdcfox
1 hour ago
Nice answer, curious to know if it is only me or push to DX is very slow?
– Raul
1 hour ago
1
@Raul It depends on the number of files involved on your file system. It can take a few seconds to a few minutes. It's definitely noticeably slower than Force.com IDE is/was, but it's also a lot better at detecting many changes. Just like building a repo, the first push is always the longest; subsequent pushes should be much faster, as it checks for local disk diff changes, but this still takes more time than other IDEs that just deploy the changed file directly.
– sfdcfox
1 hour ago
add a comment |Â
@Raul Thank you for fixing the typo! I somehow missed this during my proofreading.
– sfdcfox
1 hour ago
Nice answer, curious to know if it is only me or push to DX is very slow?
– Raul
1 hour ago
1
@Raul It depends on the number of files involved on your file system. It can take a few seconds to a few minutes. It's definitely noticeably slower than Force.com IDE is/was, but it's also a lot better at detecting many changes. Just like building a repo, the first push is always the longest; subsequent pushes should be much faster, as it checks for local disk diff changes, but this still takes more time than other IDEs that just deploy the changed file directly.
– sfdcfox
1 hour ago
@Raul Thank you for fixing the typo! I somehow missed this during my proofreading.
– sfdcfox
1 hour ago
@Raul Thank you for fixing the typo! I somehow missed this during my proofreading.
– sfdcfox
1 hour ago
Nice answer, curious to know if it is only me or push to DX is very slow?
– Raul
1 hour ago
Nice answer, curious to know if it is only me or push to DX is very slow?
– Raul
1 hour ago
1
1
@Raul It depends on the number of files involved on your file system. It can take a few seconds to a few minutes. It's definitely noticeably slower than Force.com IDE is/was, but it's also a lot better at detecting many changes. Just like building a repo, the first push is always the longest; subsequent pushes should be much faster, as it checks for local disk diff changes, but this still takes more time than other IDEs that just deploy the changed file directly.
– sfdcfox
1 hour ago
@Raul It depends on the number of files involved on your file system. It can take a few seconds to a few minutes. It's definitely noticeably slower than Force.com IDE is/was, but it's also a lot better at detecting many changes. Just like building a repo, the first push is always the longest; subsequent pushes should be much faster, as it checks for local disk diff changes, but this still takes more time than other IDEs that just deploy the changed file directly.
– sfdcfox
1 hour ago
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f238786%2fvs-code-for-salesforce-can-we-start-from-the-beginning%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
Do you want to use it with DX or directly with a regular sandbox?
– David Cheng
37 mins ago