Has anyone been able to get Rider to debug a .NET Core 2.0 (preview) program to debug within Rider (June 2017 release)?
Rider does report the following when I open my .csproj targetting .NET Core 2.0:
".NET Core version problem: .NET Core 2.x is not fully supported. Some features will not work as expected."
Am I to assume that I need to wait for a future version of Rider??
Here is the message I see when I click the de"bug" icon in Rider:
Exception in debugger process: Exception in debug session This CoreCLR debugger session has not been given enough information to start new processes for debugging. Only Attach to Running Process operation is available.
--- EXCEPTION #1/2 [InvalidOperationException]
Message = “This CoreCLR debugger session has not been given enough information to start new processes for debugging. Only Attach to Running Process operation is available.”
ExceptionPath = Root.InnerException
ClassName = System.InvalidOperationException
HResult = COR_E_INVALIDOPERATION=80131509
Source = Mono.Debugging.Win32
StackTraceString = “
at Mono.Debugging.Win32.CoreClrDebuggerSession+<>c__DisplayClass7.<OnRun>b__4 () [0x000d1] in <7eee3f4329674169b7454ce3755a1461>:0
at Mono.Debugging.Win32.MtaThread.Run (System.Action ts, System.Int32 timeout) [0x0000d] in <7eee3f4329674169b7454ce3755a1461>:0
at Mono.Debugging.Win32.CoreClrDebuggerSession.OnRun (Mono.Debugging.Client.DebuggerStartInfo startInfo) [0x00014]...