Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

The UWP example doesn't work

See original GitHub issue

Hi,

I tested the CoreHook.UWP.FileMonitor but it doesn’t work. Am I doing something wrong?

When I launch (with admin privilege) dotnet CoreHook.UWP.FileMonitor.dll Microsoft.WindowsCalculator_8wekyb3d8bbwe!App, the calculator launched but then freezed, and after some time, an exception threw and then the calculator terminated. Also tried to launch Microsoft.MinecraftUWP_8wekyb3d8bbwe!App but also freezed. When launch without admin privilege, the UWP won’t freeze or close but same exception throws.

Unhandled Exception: System.TimeoutException: Unable to wait for injection completion.
   at CoreHook.ManagedHook.Remote.InjectionHelper.WaitForInjection(Int32 InTargetPID) in D:\Documents\Visual Studio 2017\Projects\CoreHook\CoreHook.ManagedHook\Remote\InjectionLoader.cs:line 110
   at CoreHook.ManagedHook.Remote.RemoteHooking.InjectEx(Int32 hostPID, Int32 targetPID, Int32 wakeUpTID, String lbraryPath_x86, String libraryPath_x64, Boolean InCanBypassWOW64, String coreRunDll, String coreLoadDll, String coreClrPath, String coreLibrariesPath, IPipePlatform pipePlatform, IEnumerable`1 dependencies, Object[] InPassThruArgs) in D:\Documents\Visual Studio 2017\Projects\CoreHook\CoreHook.ManagedHook\Remote\RemoteHooking.cs:line 221
...

OS: Windows 10 Pro 17134 .NET Core: 2.1.2 Environment Vars: CORE_LIBRARIES and CORE_ROOT set to C:\Program Files\dotnet\shared\Microsoft.NETCore.App\2.1.2 Both corehook64.dll and CoreRunDLL64.dll are put in the same directory as CoreHook.UWP.FileMonitor.dll