Lock file location can not be read from process when Lol run in Admin mode

Open timhaines opened this issue 3 years ago • 1 comments

Describe the bug If you start LOL via run as administrator, getting the MainModule of the process raises an exception. It turns out Riot has a page telling users to run in administrator mode. Our first beta tester was doing this (on advice of a coach).

If there's another way to reliably get the current folder to read the lockfile from (I tried it hardcoded), then the LCU API works correctly.

Hardcoding the lockfile path isn't a good solution though, as the user may have installed Lol in a different location.

Oct 12 '22 07:10 timhaines

What exception is raised? Does running the app that uses LCU Sharp as admin fix the problem?

I don't maintain this project, but feel free to submit a PR to handle the exception gracefully.

Oct 16 '22 22:10 bryanhitc