The latest #JetBrains#Fleet version has dropped, and the #dotnet experience keeps improving. It's worth checking out and keeping an eye on. It’s also pretty snappy and powered by #ReSharper.
#jetbrains#resharper 2023.2 EAP 8 brings with it Assembly Diffing! If you’re wondering if the “latest” got released to production, well… guess no more! #dotnet
I think #dotnet folks are spoiled by tooling, but reading the overwhelmingly positive feedback from CLion Nova users writing #cplusplus with #ReSharper is a nice reminder of the joy great tooling can bring folks.
You might want to use JetBrains.Annotations, if you’re using Feature Folders for #aspnetcore#mvc. The JetBrains.Annotations package tells #JetBrainsRider and #ReSharper where views can be located.
Here’s a quick screenshot of how to do that. #dotnet
Top-level statements are a neat feature of #dotnet, but some implicit returns happen when you add class definitions and functions to the end of the file.
With #JetBrainsRider and #ReSharper, you can have the tooling turn an implicit return into an explicit one, so there’s no confusion about where executing code ends and definitions start. #csharp
#dotnet folks will love the new predictive #debugger in #ReSharper. It helps show predicted values and pathways your code may take based on input. This can significantly reduce debugging time. #JetBrains
The predictive #debugger in #ReSharper for #dotnet developers is pretty awesome. Rather than doing mental gymnastics, you can see potential values from branching paths. #JetBrains
Did you know you can tell #ReSharper to not trigger the “local variable is never used” warning in your #csharp projects just my renaming the variable to “unused”, “dummy”, or “_”.
It helps you add more functionality to your libraries and helps reduce the false positives in solution-wide analysis. It’s a very powerful meta-programming approach to adding value.
Reading the latest #ReSharper and #JetBrainsRider release notes makes me realize (again) that suggestions and advice are so nuanced and that it takes experts to get them right. Even then, it may take a few tries.
A few changes around the recommendations and warnings around #csharp 12 primary constructors.
The "Collection was modified" inspection in #ReSharper is quite handy. Warns you about those accidental collection updates while looping over them, resulting in a runtime error. And can fix them automatically! #csharp#dotnet
An update notice reminded me of this plugin for #Jetbrains#Rider. Every #dotnet developer should use a plugin like this. I see this one supports #Resharper too, but if there's another extension like it for Visual Studio running sans-Resharper I'd love to know in order to keep my team in check.
It has become a tool that I don't need much anymore because it has helped me so much in the past to recognize complex code