Full stops in project name bad practise?

Would it be classed as bad practise to have a solution called "Importer" and then have several projects called Importer.[projectname]

Imagine project name is like Importer.Model etc.

Is that good or not?

I want to confirm my thoughts with other developers



No, it's not bad practice, as long as you choose appropriate names.

Visual Studio will assume that the project name provides the default namespace, so for a project named Foo.Bar you'll have Foo.Bar as your namespace.

This is useful when you're working on a set of libraries that fit under a parent namespace. For example, you might want to use your company name as the first part of the namespace, and the library name for the latter part, e.g. MyCorp.MailLib, MyCorp.ReportsLib, etc.

Need Your Help

Puppet: Package Provider - what is the "query" method for?

package puppet

I am building a custom package provider, and I am not sure what the query method is supposed to return.

Convert string of hexadecimal to decimal in c

c++ c filesystems hex osdev

I am writing an operating system in C and assembly, and in implementing the EXT2 file system I have encountered a problem. I need to convert FOUR bytes of hexadecimal to decimal in c. An example wo...