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
Copy file name to clipboardExpand all lines: README.md
+13-10
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ If you want to build the vsix package yourself (also compare the [official Micro
54
54
55
55
56
56
**Inspecting the vsix package:**
57
-
If you want to inspect the contents of the vsix package e.g. for security purposes, it can be extracted using tools such as [7-zip](https://www.7-zip.org/).
57
+
If you want to inspect the contents of the vsix package e.g. for security auditing purposes, it can be extracted using tools such as [7-zip](https://www.7-zip.org/).
58
58
Note that the html and javascript files have been minimized and merged via [webpack](https://webpack.js.org/) to improve loading times.
59
59
So I suggest to read the original source from the [GitHub repository](https://github.com/Sedeniono/ADO-History-Diff) instead.
60
60
You can then build the vsix package yourself (`npm run build`, see above) and verify that the content of your manually produced vsix package is the same as in the released vsix package (from the marketplace or GitHub releases page).
@@ -81,16 +81,19 @@ Note: Changing the theme in Azure DevOps (light to dark or vice versa) might not
81
81
82
82
## Uploading the extension to Azure DevOps Server
83
83
84
-
See the [official Microsoft documentation](https://learn.microsoft.com/en-us/azure/devops/marketplace/install-extension?view=azure-devops-2022). In short, the steps are:
84
+
See the [official Microsoft documentation](https://learn.microsoft.com/en-us/azure/devops/marketplace/install-extension?view=azure-devops-2022). In short, you have to options:
85
+
1. Option 1: Direct installation from the marketplace.
86
+
In the web interface of your Azure DevOps Server, go to `Collection Settings`→`Extensions`→`Browse marketplace` (in the top right corner) → search for "Sedenion.HistoryDiff" to find the extension and click on it →`Get it free`→ select the target collection from the drop down list → hit `Install`→`Proceed to collection`.
87
+
2. Option 2: Manual upload of the vsix package.
88
+
1. Download the vsix package either from the [Microsoft marketplace](https://marketplace.visualstudio.com/items?itemName=Sedenion.HistoryDiff) or the [releases here on GitHub](https://github.com/Sedeniono/ADO-History-Diff/releases).
89
+
Both host identical files.
90
+
Then in the web interface of your Azure DevOps Server, go to `Collection Settings`→`Extensions`→`Browse local extensions` (in the top right corner) → scroll down and select `Manage extensions`→ then `Upload extension` (top right corner).
85
91
86
-
1. Get the vsix package either from the [Microsoft marketplace](https://marketplace.visualstudio.com/items?itemName=Sedenion.HistoryDiff) or the [releases here on GitHub](https://github.com/Sedeniono/ADO-History-Diff/releases).
87
-
Both host identical files.
88
-
Then in the web interface of your Azure DevOps Server, go to `Collection Settings`→`Browse local extensions` (in the top right corner) → scroll down and select `Manage extensions`→ then `Upload extension` (top right corner).
89
-
90
-
2. Afterwards, on the `Browse local extensions` page, the `History Diff` extension should have appeared. Click on it →`Get it free`→ select the target collection from the drop down list → hit `Install`→`Proceed to collection`.
92
+
2. Afterwards, on the `Browse local extensions` page, the `History Diff` extension should have appeared. Click on it →`Get it free`→ select the target collection from the drop down list → hit `Install`→`Proceed to collection`.
93
+
94
+
91
95
You need to do this once per collection.
92
-
93
-
3. Simply uploading the extension is not enough if you use the "On-premises XML" process model. See next chapters for more information.
96
+
Also, simply uploading the extension is not enough if you use the "On-premises XML" process model. See the next chapters for more information.
94
97
95
98
96
99
@@ -250,7 +253,7 @@ Apart from the import/export steps, the steps of modifying the actual XML file s
250
253
251
254
# Future ideas
252
255
* Support more artifact links.
253
-
*Fork and improve [htmldiff](https://www.npmjs.com/package/node-htmldiff) to highlight pure formatting changes.
256
+
*Show pure formatting changes. Maybe fork and try to improve [htmldiff](https://www.npmjs.com/package/node-htmldiff). Or possibly better, use Wikipedia's [VisualDiff](https://www.mediawiki.org/wiki/Special:MyLanguage/visual_diffs) from the [VisualEditor](https://github.com/wikimedia/mediawiki-extensions-VisualEditor) (but has more dependencies). Or port [DaisyDiff](https://github.com/DaisyDiff/DaisyDiff).
254
257
* Once [markdown is available in Azure DevOps work items](https://developercommunity.visualstudio.com/t/add-markdown-support-in-discussions/365826), support it.
255
258
* Show only the context of a change in longer descriptions (optionally).
0 commit comments