3 ms·
But there was no good way to edit .csproj files without an IDE and you needed to edit them for every source file you added (or moved). Now you don't have to ed
by svick 8y ago
But there was no good way to edit .csproj files without an IDE and you needed to edit them for every source file you added (or moved).
Now you don't have to edit them as often (wildcards for files), they're easier to edit by hand (because they contain almost no clutter) and there are also command line tools to edit them (like dotnet add package).
- SuddsMcDuff 8y agoWildcards have been supported for source files for many years. <Compile Include="**/*.cs" /> I was doing this back in the .NET 3.5 days. But nitpicking aside your point is well taken, the developer experience is far better with dotnet core.
- svick 8y agoAs I understand it, if you ever opened such project in VS, it would replace the wildcard with the current list of files. So the usability of that approach was very limited.
- moogly 8y agoCorrect. It wasn't really usable.
- SuddsMcDuff 8y agoAh, I see. I wasn't using VS (which is why I found the wildcard trick). It seems like VS was the issue then, and one of the reasons donet core has a better experience is because it's much less bound to VS.