-
Notifications
You must be signed in to change notification settings - Fork 6
/
Copy pathpublishing.txt
120 lines (83 loc) · 3.46 KB
/
publishing.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
publishing.txt
These are my personal notes on testing and publishing this extension.
They are mainly for my personal reference but possibly of use to someone
else helping out with development activities.
Reference Links
---------------
Guide to writing and publishing extensions:
https://code.visualstudio.com/api/working-with-extensions/publishing-extension
Packaging
---------
To package the extension for local testing, make sure the version has
been bumped in package.json, then in a COMMAND PROMPT window (the
tools do not work from a cygwin window):
D:\wrk\vscode\default-keys-windows>set PATH=%PATH%;d:\opt\node-v18.16.0
D:\wrk\vscode\default-keys-windows>npm install -g vsce
D:\wrk\vscode\default-keys-windows>vsce package
DONE Packaged: D:\wrk\vscode\default-keys-windows\default-keys-windows-0.0.5.vsix (14 files, 116.85KB)
Local Testing
-------------
Copy the VSIX file to the Linux test VM.
On the Linux VM, open the Extensions area via button on left edge, then
choose "Install from VSIX ..." from the "..." menu. Choose the VSIX file
then restart VSCode.
Check that the new bindings appear in the key bindings list and work in
the editor. The main one I test with is Ctrl+Shift+Alt+Down, which on
Windows creates a multi-line column selection. Without this extension,
on Linux it would instead duplicate the current line, but with this
extension, also creates a multi-line column selection.
Beware: Some Linux desktop environments eat these key combinations!
See README.md for workarounds.
Publishing
----------
Make sure version has been bumped in package.json and README.md and an
entry added to CHANGELOG.md.
Log in to https://dev.azure.com/smcpeak/ with MS credentials.
Go to User Settings (top right), Personal Access Tokens.
Click New Token.
Give it a name like "token-2020-05-18".
Set Organization to "All accessible organizations".
Ensure scope is "Custom defined".
Click "Show all scopes".
Scroll down to "Marketplace" and check "Acquire" and "Manage".
Click "Create".
Copy to clipboard, save to a file.
Close window with the token.
At the COMMAND PROMPT window:
D:\wrk\vscode\default-keys-windows>vsce publish -p <token>
where <token> is the actual token (paste with Ctrl+V).
Test Installation from Marketplace
----------------------------------
Check that the new version is visible at
https://marketplace.visualstudio.com/items?itemName=smcpeak.default-keys-windows
Go to Linux test VM.
Uninstall the version that was installed from VSIX.
Restart VSCode.
In extensions, search for "Windows Default Keybindings".
Should see new version there.
Install and test with Ctrl+Shift+Alt+Down.
Publish on Github
-----------------
Tag and push, e.g.:
$ git tag v0.0.5
$ git push
$ git push origin v0.0.5
Go to Releases:
https://github.com/smcpeak/vscode-default-keys-windows/releases
Draft new release, name like vscode-default-keys-windows-0.0.5.
Select tag.
Copy CHANGELOG.md fragment.
Attach VSIX file.
2022-08-31: Github now refuses to allow VSIX files to be attached,
so rename it to ZIP first.
Publish.
Publish on open-vsx
-------------------
Instructions: https://github.com/eclipse/openvsx/wiki/Publishing-Extensions
Command to publish; run at command prompt:
> npx ovsx publish default-keys-windows-0.0.5.vsix -p <token>
where <token> is an access token I might have already in a file, otherwise
need to log in to using Github OAuth at https://open-vsx.org to create a
token.
URL to check: https://open-vsx.org/extension/smcpeak/default-keys-windows
EOF