Is it a bad idea to add a period to a .Net solution file?

Question

If I was using a "Partitioned Single Solution" strategy to build my .Net projects and solutions, could anyone comment on, or share any experiences about why it would be a bad idea to include dot notation in my solution names as such...

    master.sln
    master.sub.sln

...also let me know if you think it's a good idea? Please note that I'm not looking for someone to ask me "why don't you just use underscores or dashes". I'm just curious about any specific reasons why you wouldn't want to use periods.

Thanks,
-Matt

Answer 1

No reason not to use dots. I use them all the time, particularly since our company names all projects/solutions like this:

Solutions: CompanyName.DepartmentName.Application

Projects: CompanyName.DepartmentName.Application.ProjectName

Answer 2

I think it's perfectly acceptable and have used periods many times. Just be consistent and harness your OCD.

Answer 3

I wouldn't do it because I'd find it confusing. The solutions should be capturing specific subsystems within your overall application architecture, so I would name the solutions after those subsystems. The hierarchical data is something that I would expect in the project names for the various modules.

If you have a hierarchy for solutions and a hierarchy for projects, that'd be confusing. Especially if they're different hierarchies.

Answer 4

I don't see a "problem" using dots in solution file name. I did use them in the past as well. However these days, I just use short solution file names without any dots. I find it easier to read and locate, especially from recent projects list.

I do indeed use dots for project files for organizing hierarchy.

I guess it's just a personal preference thing for solution file names.