Install vscode extension through vsix file without CLI command - visual-studio-code

I'm trying to install vscode extension vsix file by double clicking it without using CLI command as mentioned here - code --install-extension my-extension-0.0.1.vsix
The extension is not yet published and in development mode that we'd like to share for preview.
But I'm getting the following error:-
03-03-2021 13:06:46 - Microsoft VSIX Installer
03-03-2021 13:06:46 - -------------------------------------------
03-03-2021 13:06:46 - vsixinstaller.exe version:
03-03-2021 13:06:46 - 16.8.3036
03-03-2021 13:06:46 - -------------------------------------------
03-03-2021 13:06:46 - Command line parameters:
03-03-2021 13:06:46 - C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\ServiceHub\Services\Microsoft.VisualStudio.Setup.Service\VSIXInstaller.exe,C:\Users\jmadhu\Desktop\dev\CloudNativeTest\vscode-azureloadtest\vscode-azureloadtest-0.1.0.vsix
03-03-2021 13:06:46 - -------------------------------------------
03-03-2021 13:06:46 - Microsoft VSIX Installer
03-03-2021 13:06:46 - -------------------------------------------
03-03-2021 13:06:47 - Initializing Install...
03-03-2021 13:06:47 - Extension Details...
03-03-2021 13:06:47 - Identifier : vscode-azureloadtest
03-03-2021 13:06:47 - Name : Azure Load Test
03-03-2021 13:06:47 - Author : ms-azureloadtest
03-03-2021 13:06:47 - Version : 0.1.0
03-03-2021 13:06:47 - Description : Manage your Azure Cloud Native Load Tests and Resources
03-03-2021 13:06:47 - Locale : en-US
03-03-2021 13:06:47 - MoreInfoURL :
03-03-2021 13:06:47 - InstalledByMSI : False
03-03-2021 13:06:47 - SupportedFrameworkVersionRange : [0.0,2147483647.2147483647]
03-03-2021 13:06:47 -
03-03-2021 13:06:47 - SignatureState : Unsigned
03-03-2021 13:06:47 - Supported Products :
03-03-2021 13:06:47 - Microsoft.VisualStudio.Code
03-03-2021 13:06:47 - Version :
03-03-2021 13:06:47 -
03-03-2021 13:06:47 - References :
03-03-2021 13:06:47 - Signature Details...
03-03-2021 13:06:47 - Extension is not signed.
03-03-2021 13:06:47 -
03-03-2021 13:06:47 - Searching for applicable products...
03-03-2021 13:06:47 - Found installed product - Global Location
03-03-2021 13:06:47 - Found installed product - Visual Studio Professional 2019
03-03-2021 13:06:47 - VSIXInstaller.NoApplicableSKUsException: One or more extensions are for Visual Studio Code. Try installing them in Visual Studio Code.
at VSIXInstaller.ExtensionService.GetInstallableDataImpl(IInstallableExtension extension, String extensionPackParentName, Boolean isRepairSupported, IStateData stateData, IEnumerable`1& skuData)
at VSIXInstaller.ExtensionService.GetInstallableData(String vsixPath, String extensionPackParentName, Boolean isRepairSupported, IStateData stateData, IEnumerable`1& skuData)
at VSIXInstaller.ExtensionPackService.IsExtensionPack(IStateData stateData, Boolean isRepairSupported)
at VSIXInstaller.ExtensionPackService.ExpandExtensionPackToInstall(IStateData stateData, Boolean isRepairSupported)
at VSIXInstaller.App.Initialize(Boolean isRepairSupported)
at VSIXInstaller.App.Initialize()
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)
Ques: Can we install vsix file (unpublished extension) without using CLI command? If yes, what are the possible ways?

You can only install via menu items,
"You can manually install a VS Code extension packaged in a .vsix
file. Using the Install from VSIX command in the Extensions view
command drop-down, or the Extensions: Install from VSIX command in the
Command Palette, point to the .vsix file."
from https://code.visualstudio.com/docs/editor/extension-gallery#_install-from-a-vsix
You cannot double click such files to install in Windows Explorer, because Visual Studio registers another tool (aka Microsoft VSIX Installer) there, which won't work for VSCode.

Related

The pgAdmin 4 server could not be contacted in Linux Mint 20.2

Folks i just installed pgAdmin 4 from here. But when i launch the application, it crashed, throwing me the following me error:
The pgAdmin 4 server could not be contacted:
pgAdmin Runtime Environment
--------------------------------------------------------
Python Path: "/usr/pgadmin4/venv/bin/python3"
Runtime Config File: "/home/toastedguy2/.config/pgadmin/runtime_config.json"
pgAdmin Config File: "/usr/pgadmin4/web/config.py"
Webapp Path: "/usr/pgadmin4/web/pgAdmin4.py"
pgAdmin Command: "/usr/pgadmin4/venv/bin/python3 -s /usr/pgadmin4/web/pgAdmin4.py"
Environment:
- GJS_DEBUG_TOPICS: JS ERROR;JS LOG
- LANGUAGE: en_US
- USER: toastedguy2
- XDG_SEAT: seat0
- XDG_SESSION_TYPE: x11
- SSH_AGENT_PID: 1388
- SHLVL: 0
- HOME: /home/toastedguy2
- DESKTOP_SESSION: cinnamon
- GIO_LAUNCHED_DESKTOP_FILE: /usr/share/applications/pgadmin4.desktop
- GTK_MODULES: gail:atk-bridge
- XDG_SEAT_PATH: /org/freedesktop/DisplayManager/Seat0
- LC_MONETARY: es_CR.UTF-8
- DBUS_SESSION_BUS_ADDRESS: unix:path=/run/user/1000/bus
- CINNAMON_VERSION: 5.0.5
- GIO_LAUNCHED_DESKTOP_FILE_PID: 2430
- MANDATORY_PATH: /usr/share/gconf/cinnamon.mandatory.path
- QT_QPA_PLATFORMTHEME: qt5ct
- LOGNAME: toastedguy2
- XDG_SESSION_CLASS: user
- DEFAULTS_PATH: /usr/share/gconf/cinnamon.default.path
- XDG_SESSION_ID: c2
- GTK_OVERLAY_SCROLLING: 1
- GNOME_DESKTOP_SESSION_ID: this-is-deprecated
- PATH: /home/toastedguy2/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
- GDM_LANG: en_US
- GTK3_MODULES: xapp-gtk3-module
- SESSION_MANAGER: local/toastedguy2-MS-7A39:#/tmp/.ICE-unix/1316,unix/toastedguy2-MS-7A39:/tmp/.ICE-unix/1316
- XDG_SESSION_PATH: /org/freedesktop/DisplayManager/Session0
- LC_ADDRESS: es_CR.UTF-8
- XDG_RUNTIME_DIR: /run/user/1000
- DISPLAY: :0
- LANG: en_US.UTF-8
- LC_TELEPHONE: es_CR.UTF-8
- XDG_CURRENT_DESKTOP: X-Cinnamon
- XDG_SESSION_DESKTOP: cinnamon
- XAUTHORITY: /home/toastedguy2/.Xauthority
- XDG_GREETER_DATA_DIR: /var/lib/lightdm-data/toastedguy2
- SSH_AUTH_SOCK: /run/user/1000/keyring/ssh
- SHELL: /bin/bash
- LC_NAME: es_CR.UTF-8
- QT_ACCESSIBILITY: 1
- GDMSESSION: cinnamon
- LC_MEASUREMENT: es_CR.UTF-8
- GPG_AGENT_INFO: /run/user/1000/gnupg/S.gpg-agent:0:1
- LC_IDENTIFICATION: es_CR.UTF-8
- GJS_DEBUG_OUTPUT: stderr
- XDG_VTNR: 7
- PWD: /home/toastedguy2
- XDG_CONFIG_DIRS: /etc/xdg/xdg-cinnamon:/etc/xdg
- XDG_DATA_DIRS: /usr/share/cinnamon:/usr/share/gnome:/home/toastedguy2/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share
- LC_NUMERIC: es_CR.UTF-8
- LC_PAPER: es_CR.UTF-8
- GDK_BACKEND: x11
- NO_AT_BRIDGE: 1
- PGADMIN_INT_PORT: 42741
- PGADMIN_INT_KEY: 06b1e235-ddd0-4070-9ac4-476a972202a2
- PGADMIN_SERVER_MODE: OFF
--------------------------------------------------------
Failed to launch pgAdmin4. Error:
Error: spawn /usr/pgadmin4/venv/bin/python3 ENOENT
How do i fixed it folks?
Notes:
My OS is: Linux Mint 20.2
PostgreSQL version: 12.8 (exact version by executing psql --version is: psql (PostgreSQL) 12.8 (Ubuntu 12.8-0ubuntu0.20.04.1).
PostgreSQL service is active.
After upgrading from Ubuntu 21.10 to Ubuntu 22.04 (and as a result upgrading Python 3.9 to 3.10), I had the same error. While at first it seemed the issue was that the python 3.9 symlinks inside /usr/pgadmin4 were no longer linking to the correct place - but fixing those was not enough to solve the issue. It turned out that there were more dependencies to take care of.
The proper solution was that I needed to update the apt source URI link inside "Ubuntu Software & Updates" to point to the newer Ubuntu jammy apt URI:
from https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/impish
to https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/jammy
As soon as I did that, and reinstalled pgadmin4-desktop and pgadmin4-server using apt remove and apt install, it had all the required dependencies and all worked.
All I had to do was:
sudo apt remove pgadmin4-server
sudo apt install pgadmin4-server
sudo apt install pgadmin4-desktop

jpackage on Windows: The system cannot find file, error 103

I am trying to package a ScalaFx app I built using jpackage and having trouble on windows (mac & linux work just fine).
I am building a fat jar using sbt assembly and then using jpackage to create a .msi however I am getting this error:
$ jpackage --win-shortcut --name krystalbull --app-version 0.1 --type msi -i target/scala-2.13/ --main-class com.krystal.bull.gui.GUI --main-jar krystal-bull-assembly-0.1.jar --icon src/main/resources/icons/krystal_bull.ico --verbose
shell: C:\Program Files\PowerShell\7\pwsh.EXE -command ". '{0}'"
env:
pkg-assembly: krystal-bull-assembly-0.1.jar
pkg-name: krystalbull
pkg-version: 0.1
JAVA_HOME_16.0.1_x64: C:\hostedtoolcache\windows\jdk\16.0.1\x64
JAVA_HOME: C:\hostedtoolcache\windows\jdk\16.0.1\x64
JAVA_HOME_16_0_1_X64: C:\hostedtoolcache\windows\jdk\16.0.1\x64
[21:10:32.469] Running candle.exe
[21:10:32.541] Running C:\Program Files (x86)\WiX Toolset v3.11\bin\candle.exe
[21:10:34.005] Running light.exe
[21:10:34.024] Running C:\Program Files (x86)\WiX Toolset v3.11\bin\light.exe
[21:10:35.848] Detected [light.exe] version [3.11.2.4516].
[21:10:35.848] Detected [candle.exe] version [3.11.2.4516].
[21:10:35.849] WiX 3.11.2.4516 detected. Enabling advanced cleanup action.
[21:10:46.540] Command:
jlink --output C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\runtime --module-path C:\\hostedtoolcache\\windows\\jdk\\16.0.1\\x64\\jmods --add-modules jdk.management.jfr,java.rmi,jdk.jdi,jdk.charsets,jdk.xml.dom,java.xml,java.datatransfer,jdk.jstatd,jdk.httpserver,java.desktop,java.security.sasl,jdk.zipfs,java.base,jdk.crypto.ec,jdk.javadoc,jdk.management.agent,jdk.jshell,jdk.editpad,jdk.jsobject,java.sql.rowset,jdk.sctp,jdk.jlink,jdk.unsupported,java.smartcardio,java.security.jgss,java.compiler,jdk.nio.mapmode,jdk.dynalink,jdk.unsupported.desktop,jdk.accessibility,jdk.security.jgss,java.sql,jdk.incubator.vector,java.xml.crypto,java.logging,java.transaction.xa,jdk.jfr,jdk.crypto.cryptoki,jdk.net,java.naming,jdk.internal.ed,java.prefs,java.net.http,jdk.compiler,jdk.naming.rmi,jdk.internal.opt,jdk.jconsole,jdk.attach,jdk.crypto.mscapi,jdk.internal.le,java.management,jdk.jdwp.agent,jdk.internal.jvmstat,jdk.incubator.foreign,java.instrument,jdk.management,jdk.security.auth,java.scripting,jdk.jdeps,jdk.jartool,jdk.jpackage,java.management.rmi,jdk.naming.dns,jdk.localedata --strip-native-commands --strip-debug --no-man-pages --no-header-files
[21:10:46.540] Output:
WARNING: Using incubator modules: jdk.incubator.vector, jdk.incubator.foreign
[21:10:46.544] Returned: 0
(loaded from file D:\a\krystal-bull\krystal-bull\src\main\resources\icons\krystal_bull.ico).
[21:10:46.560] Using default package resource WinLauncher.template [Template for creating executable properties file] (add krystalbull.properties to the resource-dir to customize).
[21:10:47.532] MSI ProductCode: c47093f7-318f-3c33-b6f9-e8a8c4adb014.
[21:10:47.533] MSI UpgradeCode: c62bde9b-3ba1-3197-8853-ba4770495959.
[21:10:47.536] Using default package resource main.wxs [Main WiX project file] (add main.wxs to the resource-dir to customize).
[21:10:47.537] Using default package resource overrides.wxi [Overrides WiX project file] (add overrides.wxi to the resource-dir to customize).
[21:10:47.540] Preparing MSI config: D:\a\krystal-bull\krystal-bull\krystalbull-0.1.msi.
[21:10:47.541] Generating MSI: D:\a\krystal-bull\krystal-bull\krystalbull-0.1.msi.
[21:10:47.552] Running C:\Program Files (x86)\WiX Toolset v3.11\bin\candle.exe in C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull
[21:10:50.004] Command:
C:\Program Files (x86)\WiX Toolset v3.11\bin\candle.exe -nologo C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\main.wxs -ext WixUtilExtension -arch x64 -out C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\wixobj\main.wixobj -dJpAppDescription=krystalbull -dJpAppVersion=0.1 -dJpProductCode=c47093f7-318f-3c33-b6f9-e8a8c4adb014 -dJpAppName=krystalbull -dJpAllowUpgrades=yes -dJpProductUpgradeCode=c62bde9b-3ba1-3197-8853-ba4770495959 -dJpIsSystemWide=yes -dJpAllowDowngrades=yes -dJpIcon=C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\krystalbull.exe -dJpAppVendor=Unknown -dJpConfigDir=C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\config
[21:10:50.004] Output:
main.wxs
[21:10:50.005] Returned: 0
[21:10:50.005] Running C:\Program Files (x86)\WiX Toolset v3.11\bin\candle.exe in C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull
[21:10:51.344] Command:
C:\Program Files (x86)\WiX Toolset v3.11\bin\candle.exe -nologo C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf -ext WixUtilExtension -arch x64 -out C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\wixobj\bundle.wixobj
[21:10:51.344] Output:
bundle.wxf
[21:10:51.346] Returned: 0
[21:10:51.348] Running C:\Program Files (x86)\WiX Toolset v3.11\bin\light.exe in C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull
[21:10:53.013] Command:
C:\Program Files (x86)\WiX Toolset v3.11\bin\light.exe -nologo -spdb -ext WixUtilExtension -out D:\a\krystal-bull\krystal-bull\krystalbull-0.1.msi -sice:ICE27 -loc C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\MsiInstallerStrings_en.wxl -cultures:en-us C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\wixobj\main.wixobj C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\wixobj\bundle.wixobj
[21:10:53.015] Output:
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(41) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\FileMenu$anon$2.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(56) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\dialog\ViewEventDialog$anon$10$anon$21$anonfun$lessinit$greater$1.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(71) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\SettingsMenu$anon$5.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(111) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\dialog\ViewEventDialog$anon$4.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(116) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\home\HomePane$anon$4.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(151) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\home\HomePane$anon$28.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(206) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\dialog\CreateNumericEventDialog$anon$6.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(221) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\home\HomePane$anon$10$anon$16.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(226) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\landing\LandingPane$anon$5.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(236) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\dialog\ViewEventDialog$anon$10.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(256) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\dialog\ViewEventDialog$anon$10$anon$22.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(271) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\dialog\CreateEnumEventDialog$anon$12$anon$13$anon$14.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(301) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\TaskRunner$anon$1$anon$2.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(336) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\home\HomePane$anon$10$anon$11.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(356) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\dialog\ViewEventDialog$anon$10$anon$16.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(366) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\dialog\CreateNumericEventDialog$anon$4.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(391) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\ViewMenu$anon$9.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(411) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\dialog\CreateEnumEventDialog$anon$1.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(426) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\HelpMenu$anon$13.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(436) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\landing\LandingPane$anon$7.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(451) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\home\HomePane$anon$21.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(461) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\ViewMenu$anon$9$anon$10.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(476) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\home\HomePane$anon$2.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(531) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\home\HomePane$anon$10$anon$14.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(546) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\dialog\ViewEventDialog$anon$2.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(556) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\dialog\CreateEnumEventDialog$anon$12$anon$15$anon$17.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(561) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\home\HomePane$anon$17.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(596) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\GUI$anon$1.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(601) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\home\HomePane$anon$23.class'.
C:\Users\runneradmin\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\bundle.wxf(631) : error LGHT0103 : The system cannot find the file 'C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull\app\classes\com\krystal\bull\gui\home\HomePane$anon$18.class'.
.. more of the same ..
[21:10:53.019] Returned: 103
[21:10:53.020] java.io.IOException: Command [C:\Program Files (x86)\WiX Toolset v3.11\bin\light.exe, -nologo, -spdb, -ext, WixUtilExtension, -out, D:\a\krystal-bull\krystal-bull\krystalbull-0.1.msi, -sice:ICE27, -loc, C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\MsiInstallerStrings_en.wxl, -cultures:en-us, C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\wixobj\main.wixobj, C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\wixobj\bundle.wixobj] in C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull exited with 103 code
at jdk.jpackage/jdk.jpackage.internal.Executor.executeExpectSuccess(Executor.java:91)
at jdk.jpackage/jdk.jpackage.internal.WixPipeline.execute(WixPipeline.java:135)
at jdk.jpackage/jdk.jpackage.internal.WixPipeline.buildMsi(WixPipeline.java:99)
at jdk.jpackage/jdk.jpackage.internal.WinMsiBundler.buildMSI(WinMsiBundler.java:521)
at jdk.jpackage/jdk.jpackage.internal.WinMsiBundler.execute(WinMsiBundler.java:386)
at jdk.jpackage/jdk.jpackage.internal.Arguments.generateBundle(Arguments.java:664)
at jdk.jpackage/jdk.jpackage.internal.Arguments.processArguments(Arguments.java:538)
at jdk.jpackage/jdk.jpackage.main.Main.execute(Main.java:98)
at jdk.jpackage/jdk.jpackage.main.Main.main(Main.java:52)
[21:10:53.512] jdk.jpackage.internal.PackagerException: java.io.IOException: Command [C:\Program Files (x86)\WiX Toolset v3.11\bin\light.exe, -nologo, -spdb, -ext, WixUtilExtension, -out, D:\a\krystal-bull\krystal-bull\krystalbull-0.1.msi, -sice:ICE27, -loc, C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\MsiInstallerStrings_en.wxl, -cultures:en-us, C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\wixobj\main.wixobj, C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\wixobj\bundle.wixobj] in C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull exited with 103 code
at jdk.jpackage/jdk.jpackage.internal.WinMsiBundler.execute(WinMsiBundler.java:389)
at jdk.jpackage/jdk.jpackage.internal.Arguments.generateBundle(Arguments.java:664)
at jdk.jpackage/jdk.jpackage.internal.Arguments.processArguments(Arguments.java:538)
at jdk.jpackage/jdk.jpackage.main.Main.execute(Main.java:98)
at jdk.jpackage/jdk.jpackage.main.Main.main(Main.java:52)
Caused by: java.io.IOException: Command [C:\Program Files (x86)\WiX Toolset v3.11\bin\light.exe, -nologo, -spdb, -ext, WixUtilExtension, -out, D:\a\krystal-bull\krystal-bull\krystalbull-0.1.msi, -sice:ICE27, -loc, C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\config\MsiInstallerStrings_en.wxl, -cultures:en-us, C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\wixobj\main.wixobj, C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\wixobj\bundle.wixobj] in C:\Users\RUNNER~1\AppData\Local\Temp\jdk.jpackage17983400798231933520\images\win-msi.image\krystalbull exited with 103 code
at jdk.jpackage/jdk.jpackage.internal.Executor.executeExpectSuccess(Executor.java:91)
at jdk.jpackage/jdk.jpackage.internal.WixPipeline.execute(WixPipeline.java:135)
at jdk.jpackage/jdk.jpackage.internal.WixPipeline.buildMsi(WixPipeline.java:99)
at jdk.jpackage/jdk.jpackage.internal.WinMsiBundler.buildMSI(WinMsiBundler.java:521)
at jdk.jpackage/jdk.jpackage.internal.WinMsiBundler.execute(WinMsiBundler.java:386)
... 4 more
Error: Process completed with exit code 1.
Unfortunately this a bug in jpackage itself for windows
jpackage does not properly escape class file names for the WIX pre-processor.
See:
https://github.com/wixtoolset/issues/issues/6734
Bug tracker for the issue on openjdk:
https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8282351
jpackage fails on Windows when application name differs from installer name as mentioned in the issue here
It works for me if I specify the same argument to --name is I specified for the app image.
(The same name as for the app-image command, but you might want to change the name).

How to solution the following error when build EmulatorPkg ?

when I run build -p EmulatorPkg\EmulatorPkg.dsc -t VS2019 -a X64, it show the following error
LINK : warning LNK4108:ָ /ALIGN ûָ /DRIVERӳܲ
LINK : warning LNK4001: δָļʹÿ
LINK : warning LNK4068: δָ /MACHINEĬΪ X86
LINK : error LNK2001: ޷ⲿ _ModuleEntryPoint
d:\edk2\edk2\Build\EmulatorX64\DEBUG_VS2019\X64\WinHost.lib : fatal error LNK1120: 1 ޷ⲿ
NMAKE : fatal error U1077: "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\
MSVC\14.25.28610\bin\Hostx86\x64\link.exe": ش롰0x460
Stop.
Building ... d:\edk2\edk2\EmulatorPkg\BootModePei\BootModePei.inf [X64]
build.py...
: error 7000: Failed to execute command
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.25.28610\bin
\Hostx86\x86\nmake.exe /nologo tbuild [d:\edk2\edk2\Build\EmulatorX64\DEBUG_VS2019\X64\EmulatorPkg\Win
\Host\WinHost]
build.py...
: error F002: Failed to build module
d:\edk2\edk2\EmulatorPkg\Win\Host\WinHost.inf [X64, VS2019, DEBUG]
- Failed -
Build end time: 22:18:35, Apr.07 2020
Build total time: 00:00:13
but when build MdeModulePkg/MdeModulePkg.dsc, it not have any error.
The error was caused by missing support for VS2019 in this module.
Support was added upstream in commit 998d4c98b7c6 ("EmulatorPkg/WinHost: Add link flags for VS2019 tool chains.").

Write a text file in Appveyor script

I have a problem when writing a simple text file with appveyor. Here is the simple script:
version: 1.0.{build}-{branch}
shallow_clone: true
environment:
matrix:
- APPVEYOR_BUILD_WORKER_IMAGE: Visual Studio 2017
TOOLSET: msvc-14.1
ARCH: x86_64
install:
build: off
test_script:
- echo ^<Where are my symbols^> > hello.txt
- more hello.txt
This leads to an error in the console:
Build started
Fetching repository commit (2be7d4b)...OK
Total: 274 bytes in 1 files
echo ^<Where are my symbols^> > hello.txt
Command exited with code 1
I have tried the commands in on desktop but everything is working.
This escape symbol will not work this way because internally we use call before your cmd when executing command from the custom PowerShell host.
Workarounds:
Use PowerShell
test_script:
- ps: Set-Content -Value "<Where are my symbols>" -Path .\hello.txt
- more hello.txt
Check-in .cmd file with your command which uses ^ escape symbol and run it.

Running PowerShell terminal in 2.0 mode

VSCode Version: 1.16.1
OS Version: Windows Server 2012 R2 Standard
Is it possible to run the PowerShell terminal using PowerShell v2.0? I have an older SharePoint farm that requires earlier version of PowerShell and would like to run that version instead of more current versions. When I open VS Code on my server the PowerShell terminal crashes.
Here is the log of the crash.
9/18/2017 10:09:24 AM [NORMAL] - Visual Studio Code v1.16.1 64-bit
9/18/2017 10:09:24 AM [NORMAL] - PowerShell Extension v1.4.3
9/18/2017 10:09:24 AM [NORMAL] - Operating System: Windows 64-bit
9/18/2017 10:09:24 AM [NORMAL] - Language server starting --
9/18/2017 10:09:24 AM [NORMAL] - exe: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
9/18/2017 10:09:24 AM [NORMAL] - args: C:\Users\me\.vscode\extensions\ms-vscode.powershell-1.4.3\scripts\Start-EditorServices.ps1 -EditorServicesVersion '1.4.1' -HostName 'Visual Studio Code Host' -HostProfileId 'Microsoft.VSCode' -HostVersion '1.4.3' -AdditionalModules #('PowerShellEditorServices.VSCode') -BundledModulesPath 'C:\Users\me\.vscode\extensions\ms-vscode.powershell-1.4.3\modules' -EnableConsoleRepl -LogLevel 'Normal' -LogPath 'C:\Users\me\.vscode\extensions\ms-vscode.powershell-1.4.3\logs\1505754564-f1d3cfae-50af-4f74-9503-061208469b8d1505754561535\EditorServices.log' -SessionDetailsPath 'C:\Users\me\.vscode\extensions\ms-vscode.powershell-1.4.3\sessions\PSES-VSCode-10764-479503' -FeatureFlags #()
9/18/2017 10:09:25 AM [NORMAL] - powershell.exe started, pid: 6412
9/18/2017 10:09:25 AM [NORMAL] - powershell.exe terminated or terminal UI was closed
9/18/2017 10:10:25 AM [NORMAL] - Language server startup failed.
9/18/2017 10:10:25 AM [ERROR] - The language service could not be started:
9/18/2017 10:10:25 AM [ERROR] - Timed out waiting for session file to appear.
I experienced the same symptoms after updating VS Code (1.25.1) and PowerShell extension (1.8.2). Discovered that C:\Users\USERNAME.vscode\extensions\ms-vscode.powershell-1.8.2\modules\PowerShellEditorServices\Start-EditorServices.ps1 was failing to launch by looking at the logs and trying to launch it manually from a separate PowerShell instance with the same arguments. It returned the following prompt: Do you want to run software from this untrusted publisher? [V] Never run [D] Do not run [R] Run once [A] Always run [?] Help (default is "D"): indicating that the digital signature was not trusted.
To remedy this I performed the following:
Browse to the file noted in the error message above. (ex. C:\Users\USERNAME.vscode\extensions\ms-vscode.powershell-1.8.2\modules\PowerShellEditorServices\Start-EditorServices.ps1)
Right click on the file and choose Properties | Digital Signatures
Select the signature and click Details | View Certificate
Choose the Details tab and click Copy to File...
Save the file with a .CER extension.
Using the Certificates MMC Snapin, import this file into the Trusted Publishers Certificate Store on the Local Machine.
(original solution post in https://github.com/PowerShell/vscode-powershell/issues/1360 )