Visual Studio Code on Windows
Alternatively, you can also download a Zip archive, extract it and run Code from there.
Tip: Setup will add Visual Studio Code to your %PATH% , so from the console you can type ‘code .’ to open VS Code on that folder. You will need to restart your console after the installation for the change to the %PATH% environmental variable to take effect.
User setup versus system setup
VS Code 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 VS Code on Windows.
Note: When running VS Code as Administrator in a user setup installation, updates will be disabled.
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 VS Code using the system setup means that it will be available to all users in the system.
See the Download Visual Studio Code page for a complete list of available installation options.
Updates
VS Code ships monthly releases and supports auto-update when a new release is available. If you’re prompted by VS Code, accept the newest update and it will be installed (you won’t need to do anything else to get the latest bits).
Note: You can disable auto-update if you prefer to update VS Code on your own schedule.
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.
Recent Windows build
Make sure you are on a recent Windows 10 build. Check Settings > Windows Update to see if you are up-to-date.
Windows as a developer machine
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 VS Code 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.
New Windows Terminal
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 VS Code, these topics will help you learn more about VS Code:
- Additional Components — Learn how to install Git, Node.js, TypeScript, and tools like Yeoman.
- User Interface — A quick orientation to VS Code.
- User/Workspace Settings — Learn how to configure VS Code to your preferences through settings.
- Tips and Tricks — Lets you jump right in and learn how to be productive with VS Code.
Common questions
What command-line arguments are supported by the Windows Setup?
VS Code 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 VS Code after completion with /mergetasks=!runcode .
Scrolling is laggy and not smooth
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.
I’m having trouble with the installer
Try using the zip file instead of the installer. To use this, unzip VS Code in your AppData\Local\Programs folder.
Note: When VS Code is installed via a Zip file, you will need to manually update it for each release.
Icons are missing
I installed Visual Studio Code on my Windows 8 machine. Why are some icons not appearing in the workbench and editor?
VS Code 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:
- Open an Administrator Command Prompt.
- Type REG ADD HKCR\.svg /f /v «Content Type» /t REG_SZ /d image/svg+xml .
Using the Registry Editor (regedit):
- Start regedit .
- Open the HKEY_CLASSES_ROOT key.
- Find the .svg key.
- Set its Content Type Data value to image/svg+xml .
- Exit regedit .
Unable to run as admin when AppLocker is enabled
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 VS Code from an elevated terminal, you can launch code with —no-sandbox —disable-gpu-sandbox as a workaround.
Subscribe to issue #122951 to receive updates.
Working with UNC paths
Beginning with version 1.78.1 , VS Code 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 VS Code, 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 .
Note: if you are using any of the remote extensions to connect to a workspace remotely (such as SSH), the security.allowedUNCHosts has to be configured on the remote machine and not the local machine.
This change was done to improve the security when using VS Code with UNC paths. Please refer to the associated security advisory for more information.
Advanced Installer’s Complete
Integration with Microsoft
Visual Studio
Free Advanced Installer Extension for Visual Studio * Migrate Visual Studio Setup Projects MSBuild and Azure DevOps for any CI/CD pipeline * This feature is available starting with the Freeware Edition.
Start Free Trial Check All Its Capabilities Free for 30 days. All features. No credit card required.
Pure Technology’s story of migrating from Microsoft Visual Studio Setup Projects to Advanced Installer.
If you want a quality installer product that “just works” and is easy to use and packed with features, I strongly recommend Advanced Installer. In less than 15 minutes, I had an installation package that was ready to go.
Take it from me – don’t waste valuable time trying to find another solution – use Advanced Installer and spend your hours doing something more productive with your life or enjoy that time with family, friends, or just sleeping.
Scott McClannahan,
Owner of Pure Technology Inc.
Что делает visual studio installer?
Столкнулся с такой проблемой, что после установки Visual studio возникают ошибки прав доступа к файлам:
невозможно посмотреть фото штатной программой
браузер не может скачать файл
итд
.
Возникает это всё по неизвестной мне причине уже второй раз (понадобились WPF компоненты).
Управление NTFS правами ничего не решает!
Из-за этого пришлось создавать другой профиль, после первого раза, а винду так не хочется переустанавливать.
И если некоторое время не пользоваться этой студией, то она может ломается, а installer говорит, что ничего не установлено.
И как в следствие — не переустановить.
- Вопрос задан более двух лет назад
- 112 просмотров
3 комментария
Средний 3 комментария
Creating the Visual Studio Installer (VSI) for SOLIDWORKS application
Download the Microsoft Visual Studio Installer Projects Extension from Visual Studio Marketplace. Find the version which matches your Visual Studio version.
It is recommended to close current session of Visual Studio when installing this extension.
Creating setup project
Add new Setup project to the solution which can be found under the Other Project Types->Visual Studio Installer section.
Configure the attributes of the installer by selection Setup project in the solution tree and changing the attributes in the properties page.
Make sure to select the correct version of the platform. Default option x86 should be changed to x64 to support 64-bit versions of SOLIDWORKS.
Adding installation files and COM registration
Click right mouse button (RMB) o the project node and select Add—>Project Output. command from the context menu.
Select the main project of the add-in in the drop down and select Primary Output option
This will allow to add the dll into the setup as well as all dependent dlls and files.
This will also register the COM objects in the dll.
Customizing installer view
Installer can be customized and new components can be added via installer views.
Adding registry entries
Registry values need to be added into the SolidWorks registry section to make SOLIDWORKS recognize the add-in.
Open the Registry View
Add the following:
And add the following fields to this key:
(default) (DWORD Value) equals to 1. Simply leave the field name empty to set it to default (do not type (default) explicitly)
Title (String Value) — value is a title of the add-in
Description (String Value) — value is a description of the add-in
In order for the add-in to be loaded at startup add the following key
Add the default DWORD field with value 1
Adding resource files
Add the resource files to the installer by RMB on the add-in project and selecting Add->Files menu command. The resource files can be used to add icon to the installer, banner images, EULA etc.
Customizing User Interface
Open the User Interface view. This view contains the list and order of all pages displayed during the installation process.
Pages can be customized, added, deleted and reordered.
Select all pages and set the banner image. Banner image displayed at the top of the installer and is a bitmap (bmp) or png file of 500×70 pixels size.
Change the banner attribute by browsing the bitmap resource added in previous step.
More pages can be added to the installer, such as End User License Agreement (EULA) or registration page.
Installing add-in
When project compiled the msi package is generated in the output directory. This package can be redistributed to the user for installing your product.
Once installed the product icon appears in the Programs and Features page of the Control Panel. The product can be repaired or uninstalled within this page.
Releasing update
When product update is required and new installer needs to be redistributed it is required to update the version of the installer.
The following message may be displayed.
It is required to change the Product Code for every new version while Upgrade Code should remain unchanged. This will allow users to upgrade without the need of uninstalling previous version of add-in (if already installed).
It is required to change the assembly versions of all changed projects otherwise the installer would not update the dlls on the target machines.