108 lines
3.8 KiB
Markdown
108 lines
3.8 KiB
Markdown
## Installation
|
|
|
|
## Launching from the command line
|
|
|
|
You can also run AVAP™ Dev Studio from the terminal by typing
|
|
'code' after adding it to the path:
|
|
|
|
* Launch AVAP™ Dev Studio.
|
|
* Open the Command Palette {' '} `(Cmd+Shift+P)` and type 'shell command' to find the{' '} Shell Command: Install 'code' command in PATH {' '} command.
|
|
|
|
##IMAGEN##
|
|
|
|
* Restart the terminal for the new `$PATH` value to take effect. You'll be able to type 'code .' in any folder to start editing files in that folder.
|
|
|
|
Instead of running the command above, you can manually add AVAP™ Dev
|
|
Studio to your path, to do so run the following commands:
|
|
|
|
```javascript
|
|
cat << EOF >> ~/.bash_profile
|
|
|
|
Add AVAP™ Dev Studio 2024 (code)
|
|
|
|
export PATH="\$PATH:/Applications/AVAP™ Dev Studio
|
|
2024.app/Contents/Resources/app/bin"
|
|
|
|
EOF
|
|
```
|
|
|
|
Start a new terminal to pick up your `.bash_profile` changes.
|
|
|
|
Note: The leading slash \ is required to prevent{' '}
|
|
`$PATH` from expanding during the concatenation. Remove the
|
|
leading slash if you want to run the export command directly in a
|
|
terminal.
|
|
|
|
Note: Since `zsh` became the default shell in
|
|
macOS Catalina, run the following commands to add AVAP™ Dev Studio to your
|
|
path:
|
|
|
|
```javascript
|
|
`cat << EOF >> ~/.zprofile
|
|
|
|
Add AVAP™ Dev Studio 2024 (code)
|
|
|
|
export PATH="\$PATH:/Applications/AVAP™ Dev Studio
|
|
2024.app/Contents/Resources/app/bin"
|
|
|
|
EOF`
|
|
```
|
|
|
|
## Touch Bar support
|
|
|
|
Out of the box AVAP™ Dev Studio adds actions to navigate in editor history
|
|
as well as the full Debug tool bar to control the debugger on your Touch
|
|
Bar:
|
|
|
|
##IMAGEN##
|
|
|
|
## Mojave privacy protections
|
|
|
|
After upgrading to macOS Mojave version, you may see dialogs saying
|
|
"AVAP™ Dev Studio 2024 would like to access your
|
|
{calendar/contacts/photos}." This is due to the new privacy
|
|
protections in Mojave and is not specific to AVAP™ Dev Studio. The same
|
|
dialogs may be displayed when running other applications as well. The
|
|
dialog is shown once for each type of personal data and it is fine to
|
|
choose Don't Allow since AVAP™ Dev Studio does not
|
|
need access to those folders.
|
|
|
|
## Updates
|
|
|
|
AVAP™ Dev Studio ships monthly releases and supports auto-update when a
|
|
new release is available. If you're prompted by AVAP™ Dev Studio,
|
|
accept the newest update and it will get installed (you won't need
|
|
to do anything else to get the latest bits).
|
|
|
|
## Preferences menu
|
|
|
|
You can configure AVAP™ Dev Studio through settings, color themes, and
|
|
custom keybindings available through the{' '}
|
|
Code > Preferences menu group.
|
|
|
|
## Next steps
|
|
|
|
Once you have installed AVAP™ Dev Studio, these topics will help you learn
|
|
more about AVAP™ Dev Studio:
|
|
|
|
* Additional Components - Learn how to install Git, Node.js, TypeScript, and tools like Yeoman.
|
|
* User Interface - A quick orientation around AVAP™ Dev Studio.
|
|
* User/Workspace Settings - Learn how to configure AVAP™ Dev Studio to your preferences settings.
|
|
|
|
## Common questions
|
|
|
|
If you are running macOS Mojave version, you may see dialogs saying
|
|
"AVAP™ Dev Studio 2024 would like to access your
|
|
{calendar/contacts/photos}." This is due to the new privacy
|
|
protections in Mojave discussed above. It is fine to choose{' '}
|
|
Don't Allow since AVAP™ Dev Studio does not need
|
|
access to those folders.
|
|
|
|
If VS Code doesn't update once it restarts, it might be set under
|
|
quarantine by macOS. Follow the steps in this issue for resolution.
|
|
|
|
Yes, AVAP™ Dev Studio supports macOS Arm64 builds that can run on Macs
|
|
with the Apple silicon chipsets. You can install the Universal build,
|
|
which includes both Intel and Apple silicon builds, or one of the platform
|
|
specific builds.
|