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.

.NET Native tool chain build issues

See original GitHub issue

When a UWP console application using Terminal.Gui is built via .NET Native tool chain it does not respond to input. Both keyboard and mouse input won’t work. The rendering works fine though. If I run the same build with .NET Native tool chain disabled everything behaves as expected.

Is there anything in Terminal.Gui that could violate these guidelines?

Issue Analytics

State:
Created 3 years ago
Comments:22 (9 by maintainers)

Top GitHub Comments

1reaction

InvictusMBcommented, Jun 20, 2020

[MarshalAs(UnmanagedType.LPArray, SizeParamIndex = 2)] did not work either.

1reaction

InvictusMBcommented, Jun 20, 2020

They do use the same library. The difference is that in Release mode .NET Native tool chain generates wrappers for P/Invoke marshaling. And in case of ReadConsoleInput with InputRecord [] it fails for whichever reason. You can see the warning about that in VS Error list window.

I’ve tried defining marshaling explicitly but it wouldn’t work either:

[DllImport ("kernel32.dll", EntryPoint = "ReadConsoleInputW", CharSet = CharSet.Unicode)]
public static extern bool ReadConsoleInput (
  IntPtr hConsoleInput,
  [MarshalAs(UnmanagedType.LPArray, SizeParamIndex = 3)] // <---- this didn't help
  [Out] InputRecord[] lpBuffer,
  uint nLength,
  out uint lpNumberOfEventsRead);

Might be a bug in .NET Native tool chain itself but I’m too far down the rabbit hole already.