fix(DotNetDllPathPatcher): correct dll path construction in Update-Exe

Milkitic · Milkitic · commit 958fb2ab9084 · 2026-01-18T14:06:23.000+08:00
The previous path construction was missing a relative path indicator (.) which could cause issues when resolving the dll path. The change ensures proper relative path resolution by prefixing with "./".
diff --git a/src/Apps/KeyAsio/DotNetDllPathPatcher.ps1 b/src/Apps/KeyAsio/DotNetDllPathPatcher.ps1
@@ -24,7 +24,7 @@ function Update-Exe {
         throw [PathTooLongException] 'old dll path is too long'
     }
 
-    $new_dll_path = "$target_path$separator$dll_name"
+    $new_dll_path = ".$separator$target_path$separator$dll_name"
     $new_bytes = [Encoding]::UTF8.GetBytes("$new_dll_path`0")
     Write-Host "Dll path Change to `"$new_dll_path`""
     if ($new_bytes.Count -gt $max_path_length) {

Original file line number	Diff line number	Diff line change
`@@ -24,7 +24,7 @@ function Update-Exe {`
`24`	`24`	`throw [PathTooLongException] 'old dll path is too long'`
`25`	`25`	`}`
`26`	`26`
`27`		`- $new_dll_path = "$target_path$separator$dll_name"`
	`27`	`+ $new_dll_path = ".$separator$target_path$separator$dll_name"`
`28`	`28`	$new_bytes = [Encoding]::UTF8.GetBytes("$new_dll_path`0")
`29`	`29`	Write-Host "Dll path Change to `"$new_dll_path`""
`30`	`30`	`if ($new_bytes.Count -gt $max_path_length) {`