My main usecase for linqpad is database interactive stuff or exploratory code with .dump().
I see this as more of a complement to that. However I have worked at places that HATED powershell and we used linqpad for almost all scripting. It worked ok.
My main usecase for linqpad is database interactive stuff or exploratory code with .dump().
I see this as more of a complement to that. However I have worked at places that HATED powershell and we used linqpad for almost all scripting. It worked ok.