[Open-Ended] Tell me about your workflow & setup.
Hey all,
I'm new to the C# space.
I have a few YoE working on web enterprise products (not C#), and looking to upskill in Asp.net / C#.
Primary goal would be to build web apps - with AWS/Azure included.
Open to all responses, but some things I'm interested to hear about things like:
- What's your setup? Which IDE / OS you use?
- What tools do you use?
- How do you / your team do testing, CI/CD, etc.
- If you were setting up a machine from scratch, what would you prioritise?
- What do you work on?
- Do you have any tips? Pain points you'd like to share?
Thanks all.
14 Replies
Not a web dev but I mainly run VSCode with C# Dev Kit, and sometimes Rider, on Linux (Mint rn). I 'work' on mostly games and compilers.
Thank you:thankuwu:
From what i've been seeing online is that people prefer using Visual Studio - mainly due to the debugger.
What's your approach for debugging in VSCode? (Is there an extension / plugin that helps with this)
Personally I never debugged in my past applications, and mostly used console.logs, so interested to hear about your experience 😆
C# Dev Kit has a built-in debugger. It's not as advanced as VS's or especially Rider's, but it's serviceable and works for most situations ime.
Considering you're on a team, Rider probably isn't applicable if your team isn't already paying for a Jetbrains license, but I personally vastly prefer Rider to Visual Studio.
Yeah - I've yet to join and see any onboarding docs, but trying to get a bit of a head start.
Thanks for the info 🙇
no problem :catcorn:
Someone else will probably come along who has more experience with web specifically, I really can't speak on that front
you can use all the standard/common tools/practices you use for dotnet development also in asp.net just that for asp you might want to have a couple extra tools for testing rest/http calls
eg postman or the couple OSS alternatives
also for authing you might want to check the different methods out
in the grand scheme tho its just "normal" stuff
also only knowing how to log but not debug is a big nono
that would be imo the first thing you have to learn
I use VS on Windows, nice and traditional. Tooling is Gitlab+Jenkins+Artifactory+JIRA.
New machine would be:
* Install chocolatey
* Get my shell environment with msys2, fish, windows terminal set up, then use yadm to get my dotfiles and other random tools installed
* Turn of all the things in Windows I don't like
I do mostly desktop apps in WPF
Win11, Rider... that's about the extent of it lol
Thanks all.
Will look into all, and yes - I do need to learn how to debug properly lol.
I've been working mostly with microservices all my career so I've never had to work with any large isolated pieces of code at a time
For a new machine? If Win11, definitely Start11 and Windhawk. Other than that, Everything, FFMPEG, ImageMagick, Bun
Oh Start11 is looking sweet, will definitely see if I can get that set up on my work machine.
Unknown User•3mo ago
Message Not Public
Sign In & Join Server To View
Thank you 🙇
About the testing, I was more curious about the strategies.
Any unit testing, e2e, integration, smoke tests, screenshot tests etc.
Unknown User•3mo ago
Message Not Public
Sign In & Join Server To View