WebStorm 2020.3 has reached the Beta milestone! You can upgrade to the latest build using the Toolbox App or from our website. (more…)

In this tutorial, we will cover both basic and advanced features of the AppCode debugger. You will learn how to halt a program execution using different types of breakpoints, examine the paused program state, step through the code, alter the program behavior without exiting the debugger session, and so on. As an example, we will take a simple SwiftUI application that loads a list of conferences from a local JSON file. You can look at how it was developed in the Create a SwiftUI application tutorial. At the moment, this application contains some bugs that we are going to find and fix using the

We’re halfway through the Early Access Program for v2020.3, with the EAP build #5 now available for download! Please try out the latest enhancements and share your feedback with us. (more…)

An important part of writing code is debugging. Despite the name this is not limited to just finding bugs in our code, but can help us to understand what the code is actually doing at runtime - often in a specific environment. While it's possible to do this to some extent using, so-called, "printf-debugging" (inserting code to write out messages and values to the console or a log file), that process is tedious, time-consuming, and very limited. Using a debugger well can make an order of magnitude difference in productivity at this stage - so it would be a shame not to learn our debugging tools

Hi everyone, The new AppCode 2020.3 EAP build is available for download from our site. Localization You can now localize strings easily in Swift code using the Localize string intention, which automatically generates NSLocalizedString and adds a key-value pair to the .strings file: NSLocalizedString statements are folded by default in the code editor: Navigation allows you to jump from code to the localization key-value pair via ⌘B. In addition, the context menu option for creating the .strings file is available in the Project view’s context menu. Debugger AppCode now displays the current

Hi everyone, The new AppCode 2020.3 EAP build is available for download from our site. Debugger This EAP delivers a heap of new features for inline watches from the IntelliJ Platform: Click on inline hint and examine the selected variable: Add new inline watches right from the editor window: All your created watches are associated with a particular context and are kept inside a new Inline Watches node in the Variables tab. You can click on any inline watch and quickly navigate to it: Project View Now you can use the Quick Definition shortcut to preview a file in the Project view before ope

Dear everyone, Today is bug-fix day! We’ve addressed several issues in both ReSharper and Rider and published the ReSharper 2020.2.3 and Rider 2020.2.3 builds. ReSharper 2020.2.3  ReSharper no longer freezes Visual Studio when the Favorite Documents extension is installed (RSRP-481224). Now you have more precise control over which Visual Studio actions can be overridden by ReSharper on the ReSharper | Options | Environment | Keyboard | Visual Studio Commands page. Rider 2020.2.3  Breakpoint icons no longer disappear from the code editor (RIDER-48535). There are a few fixes in F# support relat

This is a guest blog post from Michael Shpilt. Michael has been developing software for over 20 years. He owns the popular blog michaelscodingspot.com and recently published the book Practical Debugging for .NET Developers. In his day job, he works at OzCode, a company dedicated to improving debugging in .NET. Program hangs are some of the worst possible things you can have. They are terrible in both desktop and web applications. With desktop applications, your window freezes and the app becomes unresponsive and basically useless. This is unpleasant for technical users like us programmers, but

Rider 2020.2 has a lot of great new features for Unity, and debugging has certainly had its fair share of attention in this release. We’ve already introduced “pausepoints”, a new kind of breakpoint that puts the Unity editor into pause mode when a condition is met in code, allowing you to use the Unity Inspector to see what’s going on at that point. And in the last post, we saw how Rider can help you debug players, either standalone on the desktop, or on mobile devices and consoles, including USB support for Apple devices. Today, we’re going to look at a set of small features that will make a

The IntelliJ IDEA debugger is very helpful when it comes to improving your code. Not only does it help you to identify inconsistencies, but it also makes navigating to the responsible lines much easier. There are many ways to set a target execution line during debugging. You can use breakpoints, or step to the line using the Step Over (F8), Step Into (F7), and Run to Cursor (⌥F9) commands. But what if you want to jump to a particular line and set an execution point there, without executing the preceding code? Surprisingly, at the moment you can only do this with the help of workarounds, and t

Rider 2020.2 is now available! To mark this great news we’ve put together a full list of the new features and under the hood improvements that are in store for you. Let’s dive in! Download Rider 2020.2 Debugger The new release brings significant changes to the debugger API. They allow us to perform super-lazy value calculations with better interruption and custom value representation. We've also added data breakpoints. Finally, the Pin to Frame feature lets you pin local variables to the frame. Localization Manager We’re proud to introduce a new tool for working with resources. With the Lo

Where and when does a value in our program change? And what's the state of values in each iteration, when debugging recursive functions? Two good questions that Rider 2020.2 EAP helps answer, with Data Breakpoints and Pin-to-Frame! (more…)