As spotted by @mzikmundhttps://www.youtube.com/watch?v=wzMMclD8QsI there is a potential new slnx format coming to Visual Studio, which is very welcome, but it might not be MSBuild based which is quite an unexpected and unproductive solution (haha 😁)
Note that, it's not like I love MSBuild, but it is what we have today for authoring and building projects in VS/cmdline and so, let's not repeat the project.json mistake. 👀
@xoofx@mzikmund I think it would be awesome if they just used msbuild, but we do need to remember there are lots of teams out there who use VS and don’t know what msbuild is (probably… I haven’t actually asked)
@davidwengier@xoofx@mzikmund I would posit that this isn’t a great argument since Visual Studio recently adopted the Unreal Engine “uproject” format as a first-class citizen, which means Visual Studio doesn’t need “one solution file to rule them all”. It’s just a choice.
(Also I’ve never heard of “uproject”, so a great example of how little authority I have while writing these toots, just in case anyone thought otherwise. Love you all)
@davidwengier@nietras@xoofx@mzikmund There’s a big difference when you set up an expectation and then break it, versus never making the promise in the first place. Am I wrong?
Let me put it in these terms: I suspect it’s possible for someone to work on the IntelliJ platform and not know what .NET is, let alone MSBuild, or have an account on GitHub. The same is theoretically true for someone who works on parts of VS.
In fact the solution file reading code in VS was rewritten in C# within the last year or so, but was entirely C++ before that.
@davidwengier@nietras@xoofx@mzikmund Perhaps, but most .NET folks start with a solution file, and it’s a format that is synonymous with .NET projects or C++ projects (less likely). I can’t remember ever working on a production .NET app without a .sln file.
The IntelliJ argument doesn’t work since IntelliJ doesn’t require any solution files. It just reads your directory, and you’re good to go. Also, no IntelliJ files are required to complete your project. (1/2)
@khalidabuhakmeh@nietras@xoofx@mzikmund you’re preaching to the choir. “dotnet new” doesn’t create a solution file so why do I need one? VS doesn’t need solution files and can open a folder, but the experience is nowhere near as good, why?
I wish all of these things were fixed, I wish everyone could be happy, and everything could be better. Sadly it’s a huge company made of lots of tiny teams.
Which is why “just use msbuild” sadly isn’t an option. is not necessarily the slam dunk win that we all think it would be.
@KirillOsenkov@khalidabuhakmeh@nietras@xoofx@mzikmund yeah, that was a poor choice of words. I have no doubt the idea was part of the discussions (I wasn’t though, so just guessing), so it definitely is/was “an option”, it’s just not surprising to me that it isn’t a slam dunk answer to the VS team.
Add comment