@@codingflamingoWe use WSL2 for our projects at my work. I managed to get it working by just opening in Rider with \\WSL$ path. Don’t use the remote connection it sucks. The problem is I’m trying to figure out how to debug docker compose containers
To be fair, this was running a massive project. For smaller projects it uses around 4 gb or less. Just wanted to show the extremes since some people's codebases grow to be that big
Been a fan of Rider for about 2 years. Didn't know about the paste json as classes so thanks for that :)
Have you tried using Rider with project repo in WSL2? I know it’s not common most people use in Windows to develop in C# but WSL2 is good.
I was trying to do some WSL2 work and couldn't get rider to work so moved back that day to vs. is there a good way to do it?
@@codingflamingoWe use WSL2 for our projects at my work. I managed to get it working by just opening in Rider with \\WSL$ path. Don’t use the remote connection it sucks. The problem is I’m trying to figure out how to debug docker compose containers
They both have similar features but Rider makes your life easier.
9GB of RAM for an IDE is rough. My company is very stingy with additional RAM past the base 16GB and makes employees pay out of pocket.
To be fair, this was running a massive project. For smaller projects it uses around 4 gb or less. Just wanted to show the extremes since some people's codebases grow to be that big
If Rider is using 9GB, Visual Studio will be using more.
Wat? Better navigation? It's a copy of vs code ui