I don't know about that. I too have worked on .NET projects that were structured in very different ways.
IMO when you see a lot of variance that's a smell. There isn't an obvious or known good way to do something or there is no convention you get a lot of entropy creeping in. I find the folder/path based stuff at least has a convention or two that keep things in roughly the same shape from project to project. I prefer that this is the case than what I see with C# projects.
There's infinite variance in software applications so I expect proportional variance in how those projects are structured. The convention is to just have a single project until you need to separate. It's not that complicated.
But the point is that it has nothing to do with the language.
IMO when you see a lot of variance that's a smell. There isn't an obvious or known good way to do something or there is no convention you get a lot of entropy creeping in. I find the folder/path based stuff at least has a convention or two that keep things in roughly the same shape from project to project. I prefer that this is the case than what I see with C# projects.
Anyway, it's just my pet peeve.