Skip to content

Commit 2111e15

Browse files
committed
Update readme
1 parent 1895fa2 commit 2111e15

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
Simplifying dnSpy Debugging for DLLs
33

44
## Why do you need this?
5-
You don't! In my case, it is too annoying when I dump a DLL in .NET and cannot debug it directly. After experiencing this problem, I decided to create a kind of _helper_ for display.
5+
You don't! In my case, it is too annoying when I dump a **DLL** in **.NET** and cannot debug it directly. After experiencing this problem, I decided to create a kind of _helper_ for display.
66

77
It means that you can simply tell what should be called, and the _helper_ will do it for you. Let's see an example.
88

@@ -21,7 +21,7 @@ The ``config.json``.
2121

2222
```
2323

24-
There is a need to add the ``Name``, the MethodName, and the ``Parameters``parameter if needed.
24+
There is a need to add the ``Name``, the MethodName, and the ``Parameters`` parameter if needed.
2525

2626
In my **DLLTest** example I have three methods:
2727
```C#
@@ -44,7 +44,7 @@ public static int AddTwoValues(int val1, int val2)
4444
That's the reason my ``config.json`` is in that way.
4545

4646
## Using dnSpyDLLHelper
47-
We just need to load both files in **[dnSpy](https://github.com/dnSpyEx)**. The fastest way is to add a breakpoint on the DLL you want to debug and run the _helper_.
47+
We just need to load both files in **[dnSpy](https://github.com/dnSpyEx)**. The fastest way is to add a breakpoint on the **DLL** you want to debug and run the _helper_.
4848

4949
It should be something such as this image below:
5050

0 commit comments

Comments
 (0)