what do you mean by "at odds with the OS file system hierarchy"?
the file organization in a VS project can be totally abstracted from the underlying file structure, or it can be a 1-1 mapping. if I'm using a supported version control system, I might never need to care where the files live on disk. on the flip side, the fact that every file has a physical location mean I can also use whatever unsupported version control I want.
the OS filesystem is a pretty stable and relatively simple interface. I'm not sure how it could be made more intuitive without sacrificing flexibility.
Personally I am a big fan of haveing file system hierarchy dictate workspace heirarchy. I understand that there are cases where it might be nice to have a separate structure defined for an IDE, but that often comes with the cost of not being able to seamlessly use filesystem operations to edit the project directly. It feels more *nix-y to use the filesystem for this.
the file organization in a VS project can be totally abstracted from the underlying file structure, or it can be a 1-1 mapping. if I'm using a supported version control system, I might never need to care where the files live on disk. on the flip side, the fact that every file has a physical location mean I can also use whatever unsupported version control I want.
the OS filesystem is a pretty stable and relatively simple interface. I'm not sure how it could be made more intuitive without sacrificing flexibility.