You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. Install **Visual Studio 2019 Community 16.3+** from [here](https://visualstudio.microsoft.com/thank-you-downloading-visual-studio/?sku=Community&rel=16)
4
+
5
+
* Select **all workloads** on the first panel
6
+
* Click **Individual components**, type *Git* in the search box and select **Git for Windows** and **GitHub extension for Visual Studio**
2.*Optional:* Install the [Extensibility Essentials 2019](https://marketplace.visualstudio.com/items?itemName=MadsKristensen.ExtensibilityEssentials2019) Visual Studio extension. This includes very useful tools for obtaining command IDs and other things.
13
+
14
+
3.*Optional:* Configure the build **environment variables** required only for releasing the extension:
15
+
16
+
* Open **File Explorer**
17
+
* Navigate to the directory holding the cloned repository
18
+
***Right-click** on **buildenv.cmd** and then **Run as adminstrator**
19
+
* Press ENTER to close the CMD window when the script is finished
20
+
* Restart any Visual Studio instances or command windows to pick up the changes.
Note that we haven't published the release yet so be sure not to copy/paste the URL from the release draft. Instead, copy/paste the link above and modify the version.
19
+
20
+
6. Open the solution, set the build configuration to **RELEASE** and then manually clean and build the solution.
21
+
22
+
7. Run this command to complete the release process by copying the build artifcats to the [$/Build] folder:
23
+
24
+
`%RDBG_TOOLBIN%\builder.cmd`
25
+
26
+
8. Attach `$/Build/RaspberryDebugger.vsix** to the the release.
27
+
28
+
9. Copy/paste the SHA512 from `$/Build/RaspberryDebugger.vsix.sha512.txt** into the release notes.
29
+
30
+
10. Commit any changes and push them to GitHub using a comment like: **RELEASE: v1.0**
31
+
32
+
11. Publish the GitHub release.
33
+
34
+
12. Switch back to the **main** branch, merge the changes from the release branch and push **main** to GitHub.
35
+
36
+
13. Publish to the Visual Studio Marketplace:
37
+
38
+
a. Goto [Visual Studio MarketPlace](https://marketplace.visualstudio.com/vs)
d. Click on the **...** next to **Raspberry Debugger** and select **Edit**
42
+
e. Click the **pencil** icon next to **RaspberryDebugger.vsix** and select the new VSIX file at `$/Build/RaspberryDebugger.vsix`
43
+
f. Review and edit the description and overview as required
44
+
g. Click **Save & Upload** at the bottom of the page
45
+
46
+
------------------------------------------------
47
+
$todo(jefflill): Flesh these out:
48
+
49
+
15. Sign the extension??
50
+
51
+
------------------------------------------------
52
+
53
+
### Post Release Steps
54
+
55
+
1. Create an .ZIP archive by executing:
56
+
57
+
`%RDBG_TOOLBIN%\archive.cmd`
58
+
59
+
2. Create the next release branch from main named like: release-v1.0" and push it to GitHub.
60
+
61
+
3. Create a new GitHub release with tag like v1.0 and named like v1.0 and select the next release branch. Copy `RELEASE-TEMPLATE.md` as the initial release description and then save the draft release.
/// Initialization of the package; this method is called right after the package is sited, so this is the place
39
+
/// where you can put all the initialization code that rely on services provided by VisualStudio.
40
+
/// </summary>
41
+
/// <param name="cancellationToken">A cancellation token to monitor for initialization cancellation, which can occur when VS is shutting down.</param>
42
+
/// <param name="progress">A provider for progress updates.</param>
43
+
/// <returns>A task representing the async work of package initialization, or an already completed task if there is none. Do not return null from this method.</returns>
0 commit comments