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.

Support Windows ARM64

See original GitHub issue

Environment data

Windows ARM64 Install Windows ARM64 .NET Core SDK (NOT x86)

Steps to reproduce

Create console app
Insert a ReadLine in it, to hault execution so we can wait on the debugger being attached
Build console app at CLI
Launch app, and make sure it is waiting at the ReadLine
Attach to the right PID

Expected behavior

Debugger shows threads and any other appropriate data
breaks at breakpoint after the ReadLine once I hit enter

Actual behavior

Debugger doesn’t appear to do anything

Tried same steps launching the app with both .NET Core 3.0 x86 runtime and .NET Core 3.0 ARM64 runtime. Same experience.

My App

    class Program
    {
        static void Main(string[] args)
        {
            var pid = System.Diagnostics.Process.GetCurrentProcess().Id;
            Console.WriteLine("Hello World!");
            Console.WriteLine($"Process: {pid}");
            Console.WriteLine("Press enter to exit.");
            Console.ReadLine();
            Console.WriteLine(System.Runtime.InteropServices.RuntimeInformation.FrameworkDescription);
        }
    }

Issue Analytics

State:
Created 4 years ago
Reactions:7
Comments:51 (28 by maintainers)

Top GitHub Comments

10reactions

visschersmcommented, Aug 28, 2020

I currently use the dotnet CLI on my surface pro x to develop some net5. Though I’m very much looking forward to full support for the arm64 processors.

9reactions

kotha16commented, Nov 18, 2020

When is the official support for Windows 10 ARM64 coming…Why is this taking so long…Not having an ARM64 is really sad especially people buying surface pro x…Am not sure why msft is not looking into this