#dotnet people! I know you’re out there. What’s your dev toolkit? Things you can’t live without, you bring them with you from job to job.
Extensions, apps, keyboard configs, IDEs, CLIs, XYZs, all of it!
I might be needing these soon. 🤞
#dotnet people! I know you’re out there. What’s your dev toolkit? Things you can’t live without, you bring them with you from job to job.
Extensions, apps, keyboard configs, IDEs, CLIs, XYZs, all of it!
I might be needing these soon. 🤞
@box464 biggest one for me is Rider for my IDE. After that something like Fiddler for inspecting traffic.
Otherwise I’m pretty much a stock system kind of person.
Oh. “Just” as well instead of Make. I use this for automating a lot of things like building and deploying web apps when testing
@box464 given the option in a business context: I’m Rider for backend - the scratch area is handy for powershell scripts and other single file things I want ti mess around with, and originally I went to it over VS because I thought “its reshaprer but an IDE”, not exactly but overall its positive. For frontend its VSCode all the way, originally webstorm but there was a period a year ago where I was fighting it and the version of the vue and typescript language servers causing all manner of headaches.
Then for databases I use datagrip, handy for when I’m working with postgres, mssql and redis all in the one project.
FWIW Rider _can_ be an all in one here, but it’s bloated enough as it is and it’s good to have clear separations between them personally for me.
You’ll rarely need the CLI for most of anything outside some very niche or cutting edge things but thats up to preference, IDEs generally surface dotnet templates installed so if you’re going to work in the IDE why not.
VS community is free for non-commercial so you can always jump into that and see how it feels and learn the keymap it has, then explore rider and use the VS keymap it has so you retain the muscle memory.
@box464 Autofixture. I‘ve worked in many domain-heavy teams and Autofixture is for me the foundation to generate random domain objects in unit tests. Combine that with the object mother and object builder patterns and it’s such an incredibly powerful tool.
Writing the object builders is always just a hassle, so I wrote this thing here that does it automatically from the CLI: https://github.com/Velociraptor45/TestCodeGenerator
There’s a bit more required, but I’d be happy to point you in a direction, if needed.
dotnet run script.cs).@wiezy_kwri Ah I’m an old postman user but recently tried Bruno. Looking at insomnia, haven’t heard of that one. Thanks.
Going full command line for dotnet work, respect!