<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>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>ynx</author><text>As a very longtime iOS and Linux dev turned Windows and .NET dev (with some rust on the side) - who has used VSCode, VS, and Xamarin for multiple years - no.&lt;p&gt;There is a place for a featureful IDE with robustly implemented build, debug, and package management capabilities working out of the box with multiple languages and entrenched technologies.&lt;p&gt;I do very much like VSC and use it all the time for anything involving text, markdown, cross-platform C++, javascript, and even rust...but Visual Studio is as much of the Windows or .NET dev&amp;#x27;s toolkit as Xcode is a part of a dev in the Apple ecosystem.&lt;p&gt;VSCode is great. However, there is plenty of space for VS: it is also very strong, and has a long history of deep and extensive integration into very mature technologies. VS is still getting better year over year and while I see VSCode as competitive in some spaces, it is no contest in others. If VSCode is to replace VS, it has a very long tail of issues to address, the resolution of which would probably raise both boats anyways.</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>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>fabian2k</author><text>I mean at this point I have truly no idea what I&amp;#x27;m talking about. But I would always bet on Azure against Visual Studio in a fight. The earning potential for Azure is simply far, far higher than for Visual Studio. AWS has shown that the cloud is a recipe for printing money, and I trust Microsoft to follow the money.</text></comment>