120 lines
5.4 KiB
Markdown
120 lines
5.4 KiB
Markdown
### Installation
|
|
|
|
Alternatively, you can also download a Zip archive, extract it and run
|
|
Code from there.
|
|
|
|
### User setup versus system setup
|
|
|
|
AVAP™ Dev Studio 2024 provides both Windows user and{' '}
|
|
system level setups.
|
|
|
|
The user setup does not require Administrator privileges to run as the
|
|
location will be under your user Local AppData (
|
|
`LOCALAPPDATA` ) folder. Since it requires no elevation, the
|
|
user setup is able to provide a smoother background update experience.
|
|
This is the preferred way to install AVAP™ Dev Studio 2024 on Windows.
|
|
|
|
The system setup requires elevation to Administrator privileges to run and
|
|
will place the installation under the system's Program Files. The
|
|
in-product update flow will also require elevation, making it less
|
|
streamlined than the user setup. On the other hand, installing AVAP™ Dev
|
|
Studio 2024 using the system setup means that it will be available to all
|
|
users in the system.
|
|
|
|
See the Download AVAP™ Dev Studio 2024 page for a complete list of
|
|
available installation options.
|
|
|
|
### Updates
|
|
|
|
AVAP™ Dev Studio 2024 ships monthly releases and supports auto-update when
|
|
a new release is available. If you're prompted by AVAP™ Dev Studio
|
|
2024, accept the newest update and it will be installed (you won't
|
|
need to do anything else to get the latest bits).
|
|
|
|
### Windows Subsystem for Linux
|
|
|
|
Windows is a popular operating system and it can be a great cross-platform
|
|
development environment. This section describes cross-platform features
|
|
such as the Windows Subsystem for Linux (WSL) and the new Windows
|
|
Terminal.
|
|
|
|
Make sure you are on a recent Windows 10 build. Check{' '}
|
|
Settings > Windows Update to see if you are
|
|
up-to-date.
|
|
|
|
With WSL, you can install and run Linux distributions on Windows. This
|
|
enables you to develop and test your source code on Linux while still
|
|
working locally on your Windows machine.
|
|
|
|
When coupled with the WSL extension, you get full AVAP™ DS editing and
|
|
debugging support while running in the context of WSL.
|
|
|
|
See the Developing in WSL documentation to learn more or try the Working
|
|
in WSL introductory tutorial.
|
|
|
|
Available from the Microsoft Store, the Windows Terminal (Preview)
|
|
lets you easily open PowerShell, Command Prompt, and WSL terminals in a
|
|
multiple tab shell.
|
|
|
|
### 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 to AVAP™ Dev Studio.
|
|
* User/Workspace Settings - Learn how to configure AVAP™ Dev Studio to your preferences through settings.
|
|
* Tips and Tricks - Lets you jump right in and learn how to be productive with AVAP™ Dev Studio.
|
|
|
|
### Common questions
|
|
|
|
AVAP™ Dev Studio uses Inno Setup to create its setup package for Windows.
|
|
Thus, all the Inno Setup command-line switches are available for use.
|
|
|
|
Additionally, you can prevent the Setup from launching AVAP™ Dev Studio
|
|
after completion with `/mergetasks=!runcode` .
|
|
|
|
On certain devices, editor scrolling is not smooth but laggy for an
|
|
unpleasant experience. If you notice this issue, make sure you install the
|
|
Windows 10 October 2018 update where this issue is fixed.
|
|
|
|
Try using the zip file instead of the installer. To use this, unzip AVAP™
|
|
Dev Studio in your `AppData\Local\Programs` folder.
|
|
|
|
I installed AVAP™ Dev Studio on my Windows 8 machine. Why are some icons
|
|
not appearing in the workbench and editor?
|
|
|
|
AVAP™ Dev Studio uses SVG icons and we have found instances where the .SVG
|
|
file extension is associated with something other than{' '}
|
|
`image/svg+xml` . We're considering options to fix it, but
|
|
for now here's a workaround:
|
|
|
|
Using the Command Prompt:
|
|
|
|
Using the Registry Editor (regedit):
|
|
|
|
With the introduction of process sandboxing (discussed in this blog
|
|
post) running as administrator is currently unsupported when AppLocker
|
|
is configured due to a limitation of the runtime sandbox. If your work
|
|
requires that you run AVAP™ Dev Studio from an elevated terminal, you can
|
|
launch `code` with{' '}
|
|
`--no-sandbox --disable-gpu-sandbox` as a workaround.
|
|
|
|
Subscribe to issue #122951 to receive updates.
|
|
|
|
Beginning with version `1.78.1` , AVAP™ Dev Studio on Windows
|
|
will only allow to access UNC paths (these begin with a leading{' '}
|
|
`\\` ) that were either approved by the user on startup or
|
|
where the host name is configured to be allowed via the new{' '}
|
|
`security.allowedUNCHosts setting` .
|
|
|
|
If you rely on using UNC paths in AVAP™ Dev Studio, you can either
|
|
|
|
* configure the host to be allowed via the{' '} `security.allowedUNCHosts` setting (for example add{' '} `server-a` when you open a path such as{' '} `\\server-a\path` )
|
|
* map the UNC path as network drive and use the drive letter instead of the UNC path (documentation)
|
|
* define a global environment variable{' '} `NODE_UNC_HOST_ALLOWLIST` with the backslash-separated list of hostnames to allow, for example: `server-a\server-b` to allow the hosts `server-a` and `server-b` .
|
|
|
|
This change was done to improve the security when using AVAP™ Dev Studio
|
|
with UNC paths. Please refer to the associated security advisory for more
|
|
information.
|