Microsoft recommends CompanyName.TechnologyName[.Feature][.Design] and it
all comes down to not breaking the inheritence model if I am not mistaken.
VSN2003 however tells the compiler to use the name of the project as the
name of the .dll the project compiles to.
Developing on XP Pro in the Default Website would most commonly result in a
file system path such as...
InetPub/wwwroot/CompanyName.TechnologyName/default.aspx
....if I named the directory containing the project's files the same as the
name of the project itself, i.e the name of the project being
CompanyName.TechnologyName and the name of the directory where its file
resources are located also CompanyName.TechnologyName.
That seems to make sense to me but only on the local XP Pro development
'server.' This naming schema breaks down when deploying the project's
directory and file resources to the production web server which is provided
as a hosted service.
Its clumsy to request a page from the production server as http://
companyname.com/companyname.technologyname/default.aspx. I've never seen it
done. So how do you resolve Namespace naming, project naming and so on?
After all this time 1.1 has matured I still don't get it and haven't found
any documents that discuss this context.
<%= Clinton Gallagher
[1] http://msdn.microsoft.com/library/de...guidelines.asp 6  2866 
I think you are confusing the names of the project, solution, project
folder, assembly and namespace.
When you create a new project, you are asked to provide a name for that
project. The name you supply is the name that VS.NET uses for the solution,
project, project folder, root namespace and assembly. HOWEVER, you can
change these values after the project has been created. So, you could just
make a new project called what you'd like the project folder to be called
and then after the project is created, you can easily change the assembly
and root namespace names as well as the project and solution names.
Also, just because your local directory is called one thing, doesn't mean
that when you copy the project to the production server, you must use the
same directory name.
"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl... Microsoft recommends CompanyName.TechnologyName[.Feature][.Design] and it
all comes down to not breaking the inheritence model if I am not mistaken.
VSN2003 however tells the compiler to use the name of the project as the
name of the .dll the project compiles to.
Developing on XP Pro in the Default Website would most commonly result in
a file system path such as...
InetPub/wwwroot/CompanyName.TechnologyName/default.aspx
...if I named the directory containing the project's files the same as the
name of the project itself, i.e the name of the project being
CompanyName.TechnologyName and the name of the directory where its file
resources are located also CompanyName.TechnologyName.
That seems to make sense to me but only on the local XP Pro development
'server.' This naming schema breaks down when deploying the project's
directory and file resources to the production web server which is
provided as a hosted service.
Its clumsy to request a page from the production server as http://
companyname.com/companyname.technologyname/default.aspx. I've never seen
it done. So how do you resolve Namespace naming, project naming and so on?
After all this time 1.1 has matured I still don't get it and haven't found
any documents that discuss this context.
<%= Clinton Gallagher
[1]
http://msdn.microsoft.com/library/de...guidelines.asp
Thanks for your comments Scott.
If I create a new project using the name ArbitraryProjectName I could then
rename the root namespace to CompanyName.TechnologyName easily enough but
VSN2003 will name the assembly ArbitraryProjectName.dll. That's where I am
still hung up. What am I missing?
<%= Clinton Gallagher
"Scott M." <No****@NoSpam.com> wrote in message
news:uQ**************@tk2msftngp13.phx.gbl... I think you are confusing the names of the project, solution, project
folder, assembly and namespace.
When you create a new project, you are asked to provide a name for that
project. The name you supply is the name that VS.NET uses for the
solution, project, project folder, root namespace and assembly. HOWEVER,
you can change these values after the project has been created. So, you
could just make a new project called what you'd like the project folder to
be called and then after the project is created, you can easily change the
assembly and root namespace names as well as the project and solution
names.
Also, just because your local directory is called one thing, doesn't mean
that when you copy the project to the production server, you must use the
same directory name.
"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl... Microsoft recommends CompanyName.TechnologyName[.Feature][.Design] and it
all comes down to not breaking the inheritence model if I am not
mistaken. VSN2003 however tells the compiler to use the name of the
project as the name of the .dll the project compiles to.
Developing on XP Pro in the Default Website would most commonly result in
a file system path such as...
InetPub/wwwroot/CompanyName.TechnologyName/default.aspx
...if I named the directory containing the project's files the same as
the name of the project itself, i.e the name of the project being
CompanyName.TechnologyName and the name of the directory where its file
resources are located also CompanyName.TechnologyName.
That seems to make sense to me but only on the local XP Pro development
'server.' This naming schema breaks down when deploying the project's
directory and file resources to the production web server which is
provided as a hosted service.
Its clumsy to request a page from the production server as http://
companyname.com/companyname.technologyname/default.aspx. I've never seen
it done. So how do you resolve Namespace naming, project naming and so
on? After all this time 1.1 has matured I still don't get it and haven't
found any documents that discuss this context.
<%= Clinton Gallagher
[1]
http://msdn.microsoft.com/library/de...guidelines.asp
You can also change the assembly name.
Right click on the project and select properties. This will open the
property pages window. Under "Common Properties" -> General: You'll see
where to change the Assebmly Name and the Default Namespace. (if you change
the default namespace here you'll need to update existing files).
Dave
"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message
news:ud**************@TK2MSFTNGP10.phx.gbl... Thanks for your comments Scott.
If I create a new project using the name ArbitraryProjectName I could then
rename the root namespace to CompanyName.TechnologyName easily enough but
VSN2003 will name the assembly ArbitraryProjectName.dll. That's where I am
still hung up. What am I missing?
<%= Clinton Gallagher
"Scott M." <No****@NoSpam.com> wrote in message
news:uQ**************@tk2msftngp13.phx.gbl...I think you are confusing the names of the project, solution, project
folder, assembly and namespace.
When you create a new project, you are asked to provide a name for that
project. The name you supply is the name that VS.NET uses for the
solution, project, project folder, root namespace and assembly.
HOWEVER, you can change these values after the project has been created. So, you
could just make a new project called what you'd like the project folder
to be called and then after the project is created, you can easily change
the assembly and root namespace names as well as the project and solution
names.
Also, just because your local directory is called one thing, doesn't
mean that when you copy the project to the production server, you must use
the same directory name.
"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in
message news:%2****************@TK2MSFTNGP12.phx.gbl... Microsoft recommends CompanyName.TechnologyName[.Feature][.Design] and
it all comes down to not breaking the inheritence model if I am not
mistaken. VSN2003 however tells the compiler to use the name of the
project as the name of the .dll the project compiles to.
Developing on XP Pro in the Default Website would most commonly result
in a file system path such as...
InetPub/wwwroot/CompanyName.TechnologyName/default.aspx
...if I named the directory containing the project's files the same as
the name of the project itself, i.e the name of the project being
CompanyName.TechnologyName and the name of the directory where its file
resources are located also CompanyName.TechnologyName.
That seems to make sense to me but only on the local XP Pro development
'server.' This naming schema breaks down when deploying the project's
directory and file resources to the production web server which is
provided as a hosted service.
Its clumsy to request a page from the production server as http://
companyname.com/companyname.technologyname/default.aspx. I've never
seen it done. So how do you resolve Namespace naming, project naming and so
on? After all this time 1.1 has matured I still don't get it and
haven't found any documents that discuss this context.
<%= Clinton Gallagher
[1]
http://msdn.microsoft.com/library/de...guidelines.asp
Thanks, I'll try some of that but I sure wish somebody with a job who is
getting paid to sit around would have written some best practice articles
:-)
<%= Clinton Gallagher
"David Young" <RE******************@yahoo.com> wrote in message
news:uX**************@TK2MSFTNGP15.phx.gbl... You can also change the assembly name.
Right click on the project and select properties. This will open the
property pages window. Under "Common Properties" -> General: You'll see
where to change the Assebmly Name and the Default Namespace. (if you
change
the default namespace here you'll need to update existing files).
Dave
"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message
news:ud**************@TK2MSFTNGP10.phx.gbl... Thanks for your comments Scott.
If I create a new project using the name ArbitraryProjectName I could
then
rename the root namespace to CompanyName.TechnologyName easily enough but
VSN2003 will name the assembly ArbitraryProjectName.dll. That's where I
am
still hung up. What am I missing?
<%= Clinton Gallagher
"Scott M." <No****@NoSpam.com> wrote in message
news:uQ**************@tk2msftngp13.phx.gbl... >I think you are confusing the names of the project, solution, project
>folder, assembly and namespace.
>
> When you create a new project, you are asked to provide a name for that
> project. The name you supply is the name that VS.NET uses for the
> solution, project, project folder, root namespace and assembly. HOWEVER, > you can change these values after the project has been created. So,
> you
> could just make a new project called what you'd like the project folder to > be called and then after the project is created, you can easily change the > assembly and root namespace names as well as the project and solution
> names.
>
> Also, just because your local directory is called one thing, doesn't mean > that when you copy the project to the production server, you must use the > same directory name.
>
>
> "clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message > news:%2****************@TK2MSFTNGP12.phx.gbl...
>> Microsoft recommends CompanyName.TechnologyName[.Feature][.Design] and it >> all comes down to not breaking the inheritence model if I am not
>> mistaken. VSN2003 however tells the compiler to use the name of the
>> project as the name of the .dll the project compiles to.
>>
>> Developing on XP Pro in the Default Website would most commonly result in >> a file system path such as...
>>
>> InetPub/wwwroot/CompanyName.TechnologyName/default.aspx
>>
>> ...if I named the directory containing the project's files the same as
>> the name of the project itself, i.e the name of the project being
>> CompanyName.TechnologyName and the name of the directory where its
>> file
>> resources are located also CompanyName.TechnologyName.
>>
>> That seems to make sense to me but only on the local XP Pro
>> development
>> 'server.' This naming schema breaks down when deploying the project's
>> directory and file resources to the production web server which is
>> provided as a hosted service.
>>
>> Its clumsy to request a page from the production server as http://
>> companyname.com/companyname.technologyname/default.aspx. I've never seen >> it done. So how do you resolve Namespace naming, project naming and so
>> on? After all this time 1.1 has matured I still don't get it and haven't >> found any documents that discuss this context.
>>
>> <%= Clinton Gallagher
>>
>> [1]
>> http://msdn.microsoft.com/library/de...guidelines.asp >>
>
>
You would rename the assembly in the same location that you would rename the
root namespace, the project's properties dialog window.
"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message
news:ud**************@TK2MSFTNGP10.phx.gbl... Thanks for your comments Scott.
If I create a new project using the name ArbitraryProjectName I could then
rename the root namespace to CompanyName.TechnologyName easily enough but
VSN2003 will name the assembly ArbitraryProjectName.dll. That's where I am
still hung up. What am I missing?
<%= Clinton Gallagher
"Scott M." <No****@NoSpam.com> wrote in message
news:uQ**************@tk2msftngp13.phx.gbl...I think you are confusing the names of the project, solution, project
folder, assembly and namespace.
When you create a new project, you are asked to provide a name for that
project. The name you supply is the name that VS.NET uses for the
solution, project, project folder, root namespace and assembly. HOWEVER,
you can change these values after the project has been created. So, you
could just make a new project called what you'd like the project folder
to be called and then after the project is created, you can easily change
the assembly and root namespace names as well as the project and solution
names.
Also, just because your local directory is called one thing, doesn't mean
that when you copy the project to the production server, you must use the
same directory name.
"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in
message news:%2****************@TK2MSFTNGP12.phx.gbl... Microsoft recommends CompanyName.TechnologyName[.Feature][.Design] and
it all comes down to not breaking the inheritence model if I am not
mistaken. VSN2003 however tells the compiler to use the name of the
project as the name of the .dll the project compiles to.
Developing on XP Pro in the Default Website would most commonly result
in a file system path such as...
InetPub/wwwroot/CompanyName.TechnologyName/default.aspx
...if I named the directory containing the project's files the same as
the name of the project itself, i.e the name of the project being
CompanyName.TechnologyName and the name of the directory where its file
resources are located also CompanyName.TechnologyName.
That seems to make sense to me but only on the local XP Pro development
'server.' This naming schema breaks down when deploying the project's
directory and file resources to the production web server which is
provided as a hosted service.
Its clumsy to request a page from the production server as http://
companyname.com/companyname.technologyname/default.aspx. I've never seen
it done. So how do you resolve Namespace naming, project naming and so
on? After all this time 1.1 has matured I still don't get it and haven't
found any documents that discuss this context.
<%= Clinton Gallagher
[1]
http://msdn.microsoft.com/library/de...guidelines.asp
Thanks. I think I got it all straightened out. This MSDN document [1] helped
describe the heirarchy.
<%= Clinton Gallagher
[1] http://msdn.microsoft.com/library/de...guidelines.asp
"Scott M." <No****@NoSpam.com> wrote in message
news:u4**************@tk2msftngp13.phx.gbl... You would rename the assembly in the same location that you would rename
the root namespace, the project's properties dialog window.
"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in message
news:ud**************@TK2MSFTNGP10.phx.gbl... Thanks for your comments Scott.
If I create a new project using the name ArbitraryProjectName I could
then rename the root namespace to CompanyName.TechnologyName easily
enough but VSN2003 will name the assembly ArbitraryProjectName.dll.
That's where I am still hung up. What am I missing?
<%= Clinton Gallagher
"Scott M." <No****@NoSpam.com> wrote in message
news:uQ**************@tk2msftngp13.phx.gbl...I think you are confusing the names of the project, solution, project
folder, assembly and namespace.
When you create a new project, you are asked to provide a name for that
project. The name you supply is the name that VS.NET uses for the
solution, project, project folder, root namespace and assembly.
HOWEVER, you can change these values after the project has been created.
So, you could just make a new project called what you'd like the project
folder to be called and then after the project is created, you can
easily change the assembly and root namespace names as well as the
project and solution names.
Also, just because your local directory is called one thing, doesn't
mean that when you copy the project to the production server, you must
use the same directory name.
"clintonG" <cs*********@REMOVETHISTEXTmetromilwaukee.com> wrote in
message news:%2****************@TK2MSFTNGP12.phx.gbl...
Microsoft recommends CompanyName.TechnologyName[.Feature][.Design] and
it all comes down to not breaking the inheritence model if I am not
mistaken. VSN2003 however tells the compiler to use the name of the
project as the name of the .dll the project compiles to.
Developing on XP Pro in the Default Website would most commonly result
in a file system path such as...
InetPub/wwwroot/CompanyName.TechnologyName/default.aspx
...if I named the directory containing the project's files the same as
the name of the project itself, i.e the name of the project being
CompanyName.TechnologyName and the name of the directory where its file
resources are located also CompanyName.TechnologyName.
That seems to make sense to me but only on the local XP Pro development
'server.' This naming schema breaks down when deploying the project's
directory and file resources to the production web server which is
provided as a hosted service.
Its clumsy to request a page from the production server as http://
companyname.com/companyname.technologyname/default.aspx. I've never
seen it done. So how do you resolve Namespace naming, project naming
and so on? After all this time 1.1 has matured I still don't get it and
haven't found any documents that discuss this context.
<%= Clinton Gallagher
[1]
http://msdn.microsoft.com/library/de...guidelines.asp
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: boxboy |
last post by:
I am hoping someone from Microsoft could shed some insight into this
question.
Why did microsoft decide to use a verb based naming convtion for events
rather such as Close and Click for rather...
|
by: gilad |
last post by:
Hi, I have just released the initial beta of a C# project called
'aumplib'. aumplib is a C# namespace which is made up of a set of
classes that interface several prominent open source audio...
|
by: John Salerno |
last post by:
Does Microsoft have any naming guidelines for variables? I've been
reading their guidelines for just about every other type (methods,
parameters, properties, etc.) but nothing about variables. Are...
|
by: Richard Brown |
last post by:
I think I might be on track to a misnomer that I keep running into.
A lot of the assemblies that I reference are named "System",
"System.Drawing", etc. There are dlls, ie, system.dll and...
|
by: clintonG |
last post by:
Microsoft recommends CompanyName.TechnologyName and it
all comes down to not breaking the inheritence model if I am not mistaken.
VSN2003 however tells the compiler to use the name of the project...
|
by: UJ |
last post by:
What's the general feeling on using the using keyword versus spelling the
type out completely.
For instance, do most people put a using in so they can just say
MyNewType or do people not use...
|
by: Jonathan Wood |
last post by:
I was just wondering what naming convention most of you use for class
variables.
Underscore, "m_" prefix, camel case, capitalized, etc?
Has one style emerged as the most popular?
Thanks for...
|
by: Smithers |
last post by:
Is it common practise to begin the name of form classes with "frm" (e.g.,
frmOneForm, frmAnotherForm).
Or is that generally considered an outdated convention?
If not "frm" what is a common or...
|
by: mrashidsaleem |
last post by:
Can anyone guide me what is wrong with the naming conventions
suggested below? I know that this is not recommended by many
(including Microsoft) but I need to know what exactly is the rationale...
|
by: taylorcarr |
last post by:
A Canon printer is a smart device known for being advanced, efficient, and reliable. It is designed for home, office, and hybrid workspace use and can also be used for a variety of purposes. However,...
|
by: aa123db |
last post by:
Variable and constants
Use var or let for variables and const fror constants.
Var foo ='bar';
Let foo ='bar';const baz ='bar';
Functions
function $name$ ($parameters$) {
}
...
|
by: ryjfgjl |
last post by:
If we have dozens or hundreds of excel to import into the database, if we use the excel import function provided by database editors such as navicat, it will be extremely tedious and time-consuming...
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: BarryA |
last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: Sonnysonu |
last post by:
This is the data of csv file
1 2 3
1 2 3
1 2 3
1 2 3
2 3
2 3
3
the lengths should be different i have to store the data by column-wise with in the specific length.
suppose the i have to...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
| |
