"." in Project Name or Namespace name

B

Bob Johnson

I'm just wondering if it is perfectly acceptable to have one or more period
(.) in the name of Visual Studio projects and in namespace names?

I would hope not - but I'm having some flashbacks of the nightmares we
endured when the world went away from the old DOS 8.3 file names to long
names and a bunch of software choked when file names had multiple periods.
And yes - I understand that we're a long ways away from DOS... Just paranoid
I guess... but thought I'd ask before I get too far and have problems. I'm
wanting to put periods in the name of a new library project and I understand
there are implications for the deafult namespace etc.
 
S

Scott M.

It's not a problem at all. Yes, we are a long way from DOS now (and not in
Kansas anymore). The "dot-notation" you are refering to is considered to be
a best practice for separating notation groups.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Querying namespace where there are subfolders and "Namespace Provider=true" within a project 2
Assembly name vs. Namespace name 5
How to connect two classes in a namespace? 6
Function for transforming long file name in 8.3 format 6
Type or namespace name not found 4
'<name>' is declared in project '<projectname1>', which is not referenced by project '<projectname2> 3
Partial Update of VS.NET Project? 3
The type or namespace name 'MyClass' could not be found (are you missing a using directive or an ass 4

Top