3 ms·

Visual Studio is really good if you are doing C# development on Windows.

giancarlostoro 2y ago
MonoDevelop was also really nice. So much so, it looks like they copied it into Visual Studio for Mac???[0] In any regard, C# has some of the richest tooling I've seen for any programming language, I do wish Microsoft would invest even marginally into MonoDevelop again. [0]: https://www.monodevelop.com/ https://www.monodevelop.com/
- neonsunset 2y ago
  VS4Mac is MonoDevelop. Well, it was - VS4Mac is dead now as it has been stagnating, and at the end of its life was likely more harmful to .NET adoption by developers using macOS. Its niche is now replaced by VS Code, particularly after base C# extension switched to Roslyn LSP from Omnisharp, and, of course, Rider which has been a strong cross-platform offering for a long time. With that said, I heard only positive things about MonoDevelop back in the day and my impression from the feedback is that it was something its authors really put care into. I suppose it is part of history now. On Blazor - both Rider and VS Code support it. Contrary to the belief of slowly but surely diminishing group of developers that think .NET is still stuck in Windows land, there is nothing that ties you to Windows here.
  - pjmlp 2y ago
    Not really. The original VS4Mac was Mono Develop. Afterwards the team started to share code between Visual Studio and VS4Mac, written in .NET Standard libraries, until they started the full rewrite, using .NET Core proper with Cocoa bindings, as the team did not consider MAUI with Catalyst mature enough for the rewrite. Only to have the project cancelled and replaced by our Electron shell friend, after they reached the 1.0 of the rewrite efforts. Which still doesn't have the graphical tooling and storyboards integration from VS4Mac. Most folks are rather adopting Rider.
    - giancarlostoro 2y ago
      > Afterwards the team started to share code between Visual Studio and VS4Mac, written in .NET Standard libraries, until they started the full rewrite, using .NET Core proper with Cocoa bindings, as the team did not consider MAUI with Catalyst mature enough for the rewrite. Do you have a source for this? I really love these historical dev tidbits. Would love to read some of the talks on it. My understanding was that ultimately they used C++ code from the original VS itself for the new VS4Mac eventually.

MonoDevelop was also really nice. So much so, it looks like they copied it into Visual Studio for Mac???[0] In any regard, C# has some of the richest tooling I've seen for any programming language, I do wish Microsoft would invest even marginally into MonoDevelop again. [0]: https://www.monodevelop.com/ https://www.monodevelop.com/

neonsunset 2y ago
VS4Mac is MonoDevelop. Well, it was - VS4Mac is dead now as it has been stagnating, and at the end of its life was likely more harmful to .NET adoption by developers using macOS. Its niche is now replaced by VS Code, particularly after base C# extension switched to Roslyn LSP from Omnisharp, and, of course, Rider which has been a strong cross-platform offering for a long time. With that said, I heard only positive things about MonoDevelop back in the day and my impression from the feedback is that it was something its authors really put care into. I suppose it is part of history now. On Blazor - both Rider and VS Code support it. Contrary to the belief of slowly but surely diminishing group of developers that think .NET is still stuck in Windows land, there is nothing that ties you to Windows here.
- pjmlp 2y ago
  Not really. The original VS4Mac was Mono Develop. Afterwards the team started to share code between Visual Studio and VS4Mac, written in .NET Standard libraries, until they started the full rewrite, using .NET Core proper with Cocoa bindings, as the team did not consider MAUI with Catalyst mature enough for the rewrite. Only to have the project cancelled and replaced by our Electron shell friend, after they reached the 1.0 of the rewrite efforts. Which still doesn't have the graphical tooling and storyboards integration from VS4Mac. Most folks are rather adopting Rider.
  - giancarlostoro 2y ago
    > Afterwards the team started to share code between Visual Studio and VS4Mac, written in .NET Standard libraries, until they started the full rewrite, using .NET Core proper with Cocoa bindings, as the team did not consider MAUI with Catalyst mature enough for the rewrite. Do you have a source for this? I really love these historical dev tidbits. Would love to read some of the talks on it. My understanding was that ultimately they used C++ code from the original VS itself for the new VS4Mac eventually.