010-68421378
sales@cogitosoft.com
Your location:Home>News Center >New release

WHAT′S NEW IN RIDER (之一)

latest update:2018/04/19 Views:776
WHATS NEW IN RIDER Rider 2017.3 enables debugging third-party code and extends the debugger in many other ways, introdu...

WHAT′S NEW IN RIDER


Rider 2017.3 enables debugging third-party code and extends the debugger in many other ways, introduces a new project wizard, adds C# Interactive, polishes unit testing UI, enables out-of-the-box TSLint and CoffeeScript support, evolves Unity integration, adopts features from the latest ReSharper and IntelliJ Platform releases.


Rider 


Debugging third-party code
Sometimes, you want to debug an assembly that you don't own source code for: a control library or a legacy module that doesn't quite work as expected. Other times, you just want to know better how the .NET Framework operates.
Rider 2017.3 makes debugging external code an automatic, pain-free process. You can now step through and set breakpoints in assemblies that Rider decompiles on-the-fly. Rider already had both a .NET debugger and a .NET decompiler inside, we just had to make them interoperate seamlessly, which we did.
Whenever you're only interested in debugging your own code, you can change debugger settings to make it step over any library calls.


Smart Step Into
Debugging method chains and nested method calls gets way easier with a new debugger action, Smart Step Into.
The action helps you choose a particular call to step into, while stepping over all other calls in a line. For example, when debugging a line like Print(Filter(people, BuildPredicate(x => x.Feature, "smth")));, you can pick to specifically step intoFilter().


Return values in locals
Following popular demand, Rider learns to display function return values in theVariables view (a.k.a "locals") of the Debug tool window as you step through your code.
This is useful when the result of a method call is not stored in a local variable, for example when the method returns another method's return value, or when using method chaining.


More debugger improvements
Debugging in Rider has improved in many other ways, such as the following:
•    You can now drag-and-drop the execution pointer to an earlier or later location in code, letting you retry or skip certain logic without having to restart the application.
•    Callers of async functions are now displayed in the Frames view, restoring the async causality chain.
•    Debugger actions like Force Run To Cursor and Set Next Statement are now available via Alt+Enter during debugging sessions.
•    Code completion items in Variables and Watches views get a refreshed presentation.
•    Lambda expressions and extension methods are now supported when you debug Mono-based applications such as Xamarin or Unity.
•    Values of numeric types — decimal, float, double — are now evaluated and presented as expected.

 

 

 

Next:WHAT′S NEW IN RIDER (之二)
Prev:2D Design V2 :Graphic Design, Technical Drawing & CAD/CAM

© Copyright 2000-2023  COGITO SOFTWARE CO.,LTD. All rights reserved