While I appreciate what pre-commit hooks can do, they add overhead that I’m not sure is worth it for me in the long run.
If you’re looking at adding #ReSharper CLI as a pre-commit action to all #dotnet environments, here are the files for Husky.NET: task-runner.json and resharper-cli.csx (you’ll need to install the ReSharper CLI tools).
Have fun :)
🎉 New release alert - #ReSharper 2023.2 is here!
This version brings significant new features for #csharp and #cplusplus programming languages, and performance improvements, alongside productivity tools related to unit testing, AI Assistant, and more.
Howdy folks, We, #JetBrains, are having a #JetBrainsRider and #ReSharper release party in the next hour. Come and join us to see some of the latest features in action. Also, there’s live chat, so feel free to ask questions or drop a funny joke.
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.
Primary constructors are different than record definitions since primary constructors don’t create backing properties for parameters. #dotnet
#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
1) Dynamic Program Analysis says "this is slow"
2) Alt+Enter | Send to AI
3) AI Assistant gives correct fix (use DB filtering)
- #csharp enhancements (thanks #ReSharper)
- Customizable Project headers
- User accessibility improvements for visually impaired users.
- Structure view sorting & filtering
- Roslyn enhancements
- ARM32 support for remote debugging
@itsCupsy @suppoze Hi! Thank you for being so patient. 🖤
We are happy to introduce our new merchandise store to you: https://blog.jetbrains.com/blog/2023/06/19/introducing-the-brand-new-jetbrains-merchandise-store/
#ReSharper swag can be found here: https://www.jetbrainsmerchandise.com/brand/re-sharper.html
Below, in #JetBrainsRider, it is determined that I forgot to “Include” the related entity.
Check out more on the #JetBrains blog.
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.
Nice, #Resharper fucked up my key bindings, slowed everything down and popped up a bunch of notifications. And the most important part - I finally remembered why I didn't want to install it.
There are 1500+ code inspections to detect potential bugs, code smells, and more issues 🐛👃 Of course, you can apply one of the 1900+ quick-fixes right away, but did you know that there are other courses of action? 🤔
Learn more in our latest post 👇 https://blog.jetbrains.com/dotnet/2023/03/20/why-is-resharper-suggesting-this/?utm_campaign=resharper&utm_content=why-is-resharper-suggesting-this&utm_medium=referral&utm_source=twitter
Search - finally a centered search window! But so much superfluous text, code previews and the achingly slow response are deal breakers. Resharper instantly shows the file, class, method or symbol I’m looking for in a simple list always ordered by my recent use and magic.
* Remove redundant `.Contains` (e.g. on a `HashSet`)
* Remove redundant `.ContainsKey()` (e.g. on a `Dictionary`)
* Simplify with `.TryAdd()` when doing a `.Contains()` followed by an `.Add`
It's amazing how far it's all come because of the amazing folks at #JetBrains and their hard work.
@Nick_Craver #snyk and #GitHub #Dependabot should check the binary contents of nugets as well for the actual vulnerability. I once ran some scripts to find how many issues there are based on #resharper's nuget suggestion database. I can tell you, a lot.
Log4net was the most included binary of all.
I suspect the old, you have to add every dependency you depend on to your package.config is to blame here. No longer needed with modern <packageReference />.