<story><title>.NET Hot Reload Support via CLI</title><url>https://devblogs.microsoft.com/dotnet/net-hot-reload-support-via-cli/</url></story><parent_chain><item><author>nodejs_rulez_1</author><text>Rider is a non-starter - doesn&amp;#x27;t even have a community edition.</text></item><item><author>moogly</author><text>For many workloads (at least .NET), JetBrains Rider.&lt;p&gt;For C&amp;#x2F;C++ on Windows, well, you have VS Code and also JetBrains CLion, but IMO CLion is surprisingly rougher than Rider, even though it&amp;#x27;s older. You can get stuff done though.</text></item><item><author>creato</author><text>Has anything ever actually replaced VS?&lt;p&gt;I&amp;#x27;ve only ever used VS for hobby&amp;#x2F;side projects, and even 10 years ago it was leaps and bounds better than what I have to use for my professional day to day work now (code completion, debugger are the two things that I miss basically every day).&lt;p&gt;The tools that I use now have these features, but they&amp;#x27;re such a joke in comparison. The code completion has no notion of &amp;quot;code&amp;quot;, it&amp;#x27;s just looking for similar words.</text></item><item><author>oaiey</author><text>There are people on record that it was the Azure division head Scott Guthrie who gave permission to open source ASP.NET Core (which at the time was part of Azure). Later the asp.net team merged with the .net team and brought the open sourcing with them.&lt;p&gt;VS has no place anymore. The velocity and mindshare is with VS Code. VS with its visual designers had its place .. but desktop is dead and Xamarin competes with frameworks without costly IDEs.</text></item><item><author>fabian2k</author><text>This feels more like an internal turf war inside Microsoft. The general open source strategy with .NET Core and VS Code has been running long enough that I don&amp;#x27;t think it&amp;#x27;s just a smoke screen. But there&amp;#x27;s probably plenty of different interests inside Microsoft that are at least partially in conflict.&lt;p&gt;The Azure side probably doesn&amp;#x27;t care about selling Visual Studio, but they care about developer mindshare and reputation. The Visual Studio side seems to be in a more difficult position, I assumed they can just live from the enterprise&amp;#x2F;everyone else split and focus on enterprise-y stuff to still sell Visual Studio. But it looks a bit to me like VS Code and the .NET cli have become more of a competition than they&amp;#x27;d like.&lt;p&gt;And the worst mistake here might not have been pissing off the .NET community, but pissing of the people working on .NET for Microsoft. I mean in the end this is the same, but pissing off the people working on .NET would result in a much more thorough destruction of trust with the community in the end.&lt;p&gt;But I have zero inside knowledge here, might just be weird decisions driven by internal politics or whatever.</text></item></parent_chain><comment><author>babypuncher</author><text>This is what keeps me on Visual Studio. It&amp;#x27;s free for personal and open-source use, so I use it at home.&lt;p&gt;Since I know it and am familiar with it, I make my employer pay for a commercial license at work. In the grand scheme of things, it is not that expensive in a commercial setting.&lt;p&gt;VS Code is great, but I do not think it is a comprehensive replacement for Visual Studio proper when doing full stack .NET development.</text></comment>
<story><title>.NET Hot Reload Support via CLI</title><url>https://devblogs.microsoft.com/dotnet/net-hot-reload-support-via-cli/</url></story><parent_chain><item><author>nodejs_rulez_1</author><text>Rider is a non-starter - doesn&amp;#x27;t even have a community edition.</text></item><item><author>moogly</author><text>For many workloads (at least .NET), JetBrains Rider.&lt;p&gt;For C&amp;#x2F;C++ on Windows, well, you have VS Code and also JetBrains CLion, but IMO CLion is surprisingly rougher than Rider, even though it&amp;#x27;s older. You can get stuff done though.</text></item><item><author>creato</author><text>Has anything ever actually replaced VS?&lt;p&gt;I&amp;#x27;ve only ever used VS for hobby&amp;#x2F;side projects, and even 10 years ago it was leaps and bounds better than what I have to use for my professional day to day work now (code completion, debugger are the two things that I miss basically every day).&lt;p&gt;The tools that I use now have these features, but they&amp;#x27;re such a joke in comparison. The code completion has no notion of &amp;quot;code&amp;quot;, it&amp;#x27;s just looking for similar words.</text></item><item><author>oaiey</author><text>There are people on record that it was the Azure division head Scott Guthrie who gave permission to open source ASP.NET Core (which at the time was part of Azure). Later the asp.net team merged with the .net team and brought the open sourcing with them.&lt;p&gt;VS has no place anymore. The velocity and mindshare is with VS Code. VS with its visual designers had its place .. but desktop is dead and Xamarin competes with frameworks without costly IDEs.</text></item><item><author>fabian2k</author><text>This feels more like an internal turf war inside Microsoft. The general open source strategy with .NET Core and VS Code has been running long enough that I don&amp;#x27;t think it&amp;#x27;s just a smoke screen. But there&amp;#x27;s probably plenty of different interests inside Microsoft that are at least partially in conflict.&lt;p&gt;The Azure side probably doesn&amp;#x27;t care about selling Visual Studio, but they care about developer mindshare and reputation. The Visual Studio side seems to be in a more difficult position, I assumed they can just live from the enterprise&amp;#x2F;everyone else split and focus on enterprise-y stuff to still sell Visual Studio. But it looks a bit to me like VS Code and the .NET cli have become more of a competition than they&amp;#x27;d like.&lt;p&gt;And the worst mistake here might not have been pissing off the .NET community, but pissing of the people working on .NET for Microsoft. I mean in the end this is the same, but pissing off the people working on .NET would result in a much more thorough destruction of trust with the community in the end.&lt;p&gt;But I have zero inside knowledge here, might just be weird decisions driven by internal politics or whatever.</text></item></parent_chain><comment><author>jerriep</author><text>It is worth the money. Also, there a verious free license programs available, for example to students, open source maintainers, etc.</text></comment>