3 ms·
I don't know, this is only my personal experience but every time I check .NET related stuff some Windows or Visual Studio related thing pops out and I think "na
by esistgut 7y ago
I don't know, this is only my personal experience but every time I check .NET related stuff some Windows or Visual Studio related thing pops out and I think "nah, it's not worth it".
Not to sound negative but I can't really understand why they can't make their documentation platform agnostic like every other project on the planet.
- cypressious 7y agoComing from a Java background, I'm currently a big fan of .NET Core. The C# language has a bunch of nice features, the ASP.NET Core stack is nice to work with and I have JetBrains Rider so I don't ever need to touch Visual Studio.
- snypox 7y agoThe recent Visual Studios are actually pretty great, so far ahead of Rider.
- solarkraft 7y agoI completely understand this perspective. It is, however, completely possible to use .Net without Visual Studio once you understand a bit about and solutions. Especially .Net Core's dotnet command is a wonderful tool that allows you to do basically everything with it - it can run, compile, even run tests - completely on the command line. .Net documentation is however VERY crusty in my experience - all the fragmentation and outdatedness can very well lead to you accidentally reading and trying documentation that is 3 major changes behind, for a library version that has long been replaced. Nowhere will you find any warnings. That is hugely frustrating. Visual Studio itself also makes a very broken impression to me, although admittedly it appears to improve. Not sure whether that's going to be enough to keep Windows or .Net alive in the long term, since even Microsoft is moving to embedded Web apps now, abandoning their own 3 different UI solutions they have been pushing in the last 20 years (completely ignoring the 3rd party efforts like platform.uno, which they could probably acquire quite easily - seriously: Xamarin, but not this?!).