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

The recording of our webinar, Xamarin, MAUI and the reactive MVVM between them, with Rodney Littles, II, is now available. Subscribe to our community newsletter to receive notifications about future webinars. Xamarin Forms is the .NET cross platform technology that allows you to write an application in C# and target various operating systems, primarily mobile. The recommended architectural approach for .NET applications adhering to SOLID principles is Model-View-ViewModel (MVVM). ReactiveUI is a MVVM framework based on Reactive Extensions, which are a cross language approach to functional pro

Hello folks! With the Rider 2020.2 release out of the door, we're looking toward the future. After sharing our ReSharper 2020.3 plans earlier this week, we'll now look at our plans for Rider 2020.3. Your feedback is welcome and encouraged. The following is a set of highlighted features our team is currently working on. Let's get started. .NET 5 – Our plan is to put significant time and effort to support the upcoming release of .NET 5. While development is possible in Rider today with .NET 5, it is incomplete. .NET 5 is the future of .NET, and we want to help developers get there. More Perform

In this post, we’d like to share our plans for ReSharper 2020.3 and find out what we can do next to improve your development experience. Your feedback is always welcome! The following is a list of our priorities for the next release cycle of 2020.3. Note that these are features we’re working on – as opposed to features scheduled for delivery. Some of these might come with later versions. .NET and C# – Support for new platform and language features, like top-level statements or target-typed new expressions. We will extend our support for nullable reference types (NRT), for instance with a dedi

We all need to unit test our code to verify that it works the way it’s supposed to. Fortunately, Rider has the tools to enable you to test code more efficiently and quickly. In this post, we’ll look at using Mocha and Chai to write unit tests in TypeScript. (more…)

New bug-fix updates are available for both ReSharper and Rider. Here’s an overview of the most important changes that have been made. ReSharper 2020.2.2 Fixed a couple of false positives in nullable analysis. Fixed the default implementation of an interface from a referenced package. It is now recognized correctly (RSRP-480835). Fixed the 'Current directory' for unit tests. It is now set to the test project's 'bin' directory. Other unit testing issues that have been fixed are described below in the Rider section. The rest of the issues and details are available in ReSharper's bug tracker. Ri

Today we are introducing a new type of dataflow code analysis in ReSharper and Rider. We’ve gathered some statistics (by exploring the IL metadata of a large number of NuGet.org packages with an OSS license) and noticed that int is one of the most commonly used types for local variables. That's why this new analysis tracks the usage of values of the int type in your programs. It tracks the flow of integer values through your programs to detect useless or possibly erroneous pieces of code. It warns you about the following issues: Relational/equality operators that always evaluate to true or f

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

This month in computing history: The first instance of a computer bug was found in September 1947. It's called a bug because when this happened, it was a moth that wandered into the machine and caused the glitch. This is possibly now the world's most famous insect. Check out the log report in the link with the moth taped to the paper. It was called a log report because they didn't have bug reports yet. And it was on paper - they were made from actual logs at that time. (more…)

We've just released the Azure Toolkit for Rider 2020.2, and want to share what's new. On the feature side, you can now work with the Azurite storage emulator from within Rider. If you're developing Azure Functions, we've added code completion for timer triggers, and now auto-detect the core tools if you already have them installed. Log streaming for web- and function apps has been added, so you can see what is going on in your application from within Rider. We have also been working on our plugin infrastructure, and fixed a number of bugs. Let's have a look! Azurite storage emulator If you are

The recording of our August 25 webinar, REST - the ignored parts, with Irina Scurtu, is now available. Subscribe to our community newsletter to receive notifications about future webinars. In a world dominated by APIs, where everyone seems to implement microservices with so many paradigms and standards to choose from, REST seems to be the default option. Despite that, many of these so-called REST APIs don’t respect the guidelines and become brittle by overlooking some of the most powerful constraints. In this session, we will look over how we can design a REST API that is flexible and evolvab

If you are already using nullable reference types, you might have noticed that they can help make your code safer. But not automagically... This feature relies heavily on everything called by your code being annotated. Unannotated APIs are a big problem for nullable reference types, as they never produce warnings. Values from such calls show extremely optimistic non-null hints, even though there are no guarantees that these hints are correct. Here's a compiler issue for this problem. For example, if you are using LINQ's FirstOrDefault() method from .NET Core 3.1, the compiler not only allows y