Re: Source Tree Structure
- From: "Daniel O'Connell [C# MVP]" <onyxkirx@xxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 30 Apr 2005 14:14:15 -0500
"pearsons_11114" <pearsons11114@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0CDC4916-CA17-49D4-A35E-296EDED92C32@xxxxxxxxxxxxxxxx
> Hmm, not sure I follow. I wasn't able to find anything on "repertory", a
> term
> I'm not familiar with. But I take what you said below to mean that VS will
> follow the same convention as Java for a pre-existing source tree? For
> example, with the following source file:
>
> /com/company/xxx/yyy/MyClass.cs
>
> VS will add a namespace statement of "com.company.xxx.yyy" to the source?
No, VS will not modify any source when you load it. You can define a root
namespace for all source files you create(which defaults to the project
name), but loaded source will always remain the same.
VS will also append sub-directories to the namespace, so for a root
namespace of X, if you create a source file in a folder within the project,
you will get X.FolderName as the namespace in the file.
>
> If so, does that mean that that's the typical convention that people
> follow?
> Just looking for a consensus opinion. Thanks!
>
I follow a convention something closer to
<assem>/<sub1>/<sub2>
so for a project named OConnell.Magic with the namespace
OConnell.Magic.Wands the directory structure would be
OConnell.Magic/Wands/
and the assembly would be named OConnell.Magic. My general rule is if I want
to go above the root namespace its time to create a new assembly.
.
- References:
- Source Tree Structure
- From: pearsons_11114
- Re: Source Tree Structure
- From: Sylvain Lafontaine
- Re: Source Tree Structure
- From: pearsons_11114
- Source Tree Structure
- Prev by Date: Re: [Flags] on enum declarations
- Next by Date: Re: tags inside the methods
- Previous by thread: Re: Source Tree Structure
- Next by thread: Dynamic Buttons
- Index(es):
Relevant Pages
|