Skip to content

Update documentation links from docs.microsoft.com to learn.microsoft.com #123

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Update documentation links from docs.microsoft.com to learn.microsoft.com #123

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
6bd54c4
Update documentation links from docs.microsoft.com to learn.microsoft…
xtqqczze Sep 5, 2025
9d71406
Canonicalize
xtqqczze Sep 5, 2025
389291f
Update `.editorconfig`
xtqqczze Sep 9, 2025
759232c
Update link title to match target
xtqqczze Sep 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion .editorconfig
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,5 @@
# You can learn more about editorconfig here: https://docs.microsoft.com/en-us/visualstudio/ide/editorconfig-code-style-settings-reference
# editorconfig.org

[*]
#Core editorconfig formatting - indentation

Expand All @@ -10,6 +11,7 @@ align_multiline_parameter = true
align_multiline_argument = true

[*.cs]
# https://learn.microsoft.com/dotnet/fundamentals/code-analysis/code-style-rule-options

#Formatting - indentation options

Expand Down
3 changes: 1 addition & 2 deletions ReadMe.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,8 +54,7 @@ course. But in my opinion they are not meeting people's needs.
stop-gap addressing the pain of developing a debugger extension; they don't really solve
the larger problem. (for instance, two major shortcomings are: they are still too
low-level (you have to deal with the dbgeng COM API), and there's no REPL)
* The debugger team has recently introduce [Javascript
scripting](https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/javascript-debugger-scripting).
* The debugger team has recently introduce [JavaScript Debugger Scripting](https://learn.microsoft.com/windows-hardware/drivers/debugger/javascript-debugger-scripting).
Javascript is a much better (and more well-defined) language than the old windbg
scripting language, but I think that PowerShell has some advantages, the largest of
which is that nobody really uses a Javascript shell--PowerShell is much better as a
Expand Down