3 ms·

I tried this for a months, but eventually moved back.

• romanovcode 10y ago
  Was it because .NET was causing problems for you on Linux or because of lack of Visual Studio?
  • UK-AL 10y ago
    Because the vast majority of the ecosystem isn't .net core ready. So you end quite major libraries not being available.
• matthewking 10y ago
  I'm on my third of fourth attempt, this time it seems to have stuck, although I'm working from macOS. Every other time there was something crippling with dotnet core but so far so good this go, the only thing I've noticed is omnisharp / vscode error highlighting has started becoming a little laggy / incorrect since my project has grown, hoping I can continue though as VS.NET is the only reason I ever use windows at all.
• pweissbrod 10y ago
  +1 Assuming you've ported all of your windows tools to linux desktop... Once you start work on a regular cadence I wager you'll find all those windows hassles are traded for bevy of new ones with linux desktop. My current work jumps between .net and linux frequently. I've been lured by the notion of all work on a single OS. It is certainly possible. And I take a shot at it every 6 months or so. So far it still brings more hassle than practical benefit for me. Tools make all the difference in efficiency. And if youre short on time and working on C#/SqlServer/F# then nothing currently gets the job done faster than the older/boring tech (for me that's visualstudio/vsvim/resharper on windows 7). But I agree that SqlServer on linux + project rider may be enough to make practical cross-platform environment for my needs. This is a great conversation and worth checking in on every few months
• rocky1138 10y ago
  A much more useful comment would include why you moved back.