Microsoft recommends CompanyName.Tec hnologyName[.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.Tec hnologyName/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.Tec hnologyName and the name of the directory where its file
resources are located also CompanyName.Tec hnologyName.
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.tec hnologyname/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  2881 
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*********@RE MOVETHISTEXTmet romilwaukee.com > wrote in message
news:%2******** ********@TK2MSF TNGP12.phx.gbl. .. Microsoft recommends CompanyName.Tec hnologyName[.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.Tec hnologyName/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.Tec hnologyName and the name of the directory where its file
resources are located also CompanyName.Tec hnologyName.
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.tec hnologyname/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 ArbitraryProjec tName I could then
rename the root namespace to CompanyName.Tec hnologyName easily enough but
VSN2003 will name the assembly ArbitraryProjec tName.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******** ******@tk2msftn gp13.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*********@RE MOVETHISTEXTmet romilwaukee.com > wrote in message
news:%2******** ********@TK2MSF TNGP12.phx.gbl. .. Microsoft recommends CompanyName.Tec hnologyName[.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.Tec hnologyName/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.Tec hnologyName and the name of the directory where its file
resources are located also CompanyName.Tec hnologyName.
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.tec hnologyname/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*********@RE MOVETHISTEXTmet romilwaukee.com > wrote in message
news:ud******** ******@TK2MSFTN GP10.phx.gbl... Thanks for your comments Scott.
If I create a new project using the name ArbitraryProjec tName I could then
rename the root namespace to CompanyName.Tec hnologyName easily enough but
VSN2003 will name the assembly ArbitraryProjec tName.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******** ******@tk2msftn gp13.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*********@RE MOVETHISTEXTmet romilwaukee.com > wrote in
message news:%2******** ********@TK2MSF TNGP12.phx.gbl. .. Microsoft recommends CompanyName.Tec hnologyName[.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.Tec hnologyName/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.Tec hnologyName and the name of the directory where its file
resources are located also CompanyName.Tec hnologyName.
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.tec hnologyname/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.co m> wrote in message
news:uX******** ******@TK2MSFTN GP15.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*********@RE MOVETHISTEXTmet romilwaukee.com > wrote in message
news:ud******** ******@TK2MSFTN GP10.phx.gbl... Thanks for your comments Scott.
If I create a new project using the name ArbitraryProjec tName I could
then
rename the root namespace to CompanyName.Tec hnologyName easily enough but
VSN2003 will name the assembly ArbitraryProjec tName.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******** ******@tk2msftn gp13.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*********@RE MOVETHISTEXTmet romilwaukee.com > wrote in message > news:%2******** ********@TK2MSF TNGP12.phx.gbl. ..
>> Microsoft recommends CompanyName.Tec hnologyName[.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.Tec hnologyName/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.Tec hnologyName and the name of the directory where its
>> file
>> resources are located also CompanyName.Tec hnologyName.
>>
>> 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.tec hnologyname/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*********@RE MOVETHISTEXTmet romilwaukee.com > wrote in message
news:ud******** ******@TK2MSFTN GP10.phx.gbl... Thanks for your comments Scott.
If I create a new project using the name ArbitraryProjec tName I could then
rename the root namespace to CompanyName.Tec hnologyName easily enough but
VSN2003 will name the assembly ArbitraryProjec tName.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******** ******@tk2msftn gp13.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*********@RE MOVETHISTEXTmet romilwaukee.com > wrote in
message news:%2******** ********@TK2MSF TNGP12.phx.gbl. .. Microsoft recommends CompanyName.Tec hnologyName[.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.Tec hnologyName/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.Tec hnologyName and the name of the directory where its file
resources are located also CompanyName.Tec hnologyName.
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.tec hnologyname/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******** ******@tk2msftn gp13.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*********@RE MOVETHISTEXTmet romilwaukee.com > wrote in message
news:ud******** ******@TK2MSFTN GP10.phx.gbl... Thanks for your comments Scott.
If I create a new project using the name ArbitraryProjec tName I could
then rename the root namespace to CompanyName.Tec hnologyName easily
enough but VSN2003 will name the assembly ArbitraryProjec tName.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******** ******@tk2msftn gp13.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*********@RE MOVETHISTEXTmet romilwaukee.com > wrote in
message news:%2******** ********@TK2MSF TNGP12.phx.gbl. ..
Microsoft recommends CompanyName.Tec hnologyName[.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.Tec hnologyName/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.Tec hnologyName and the name of the directory where its file
resources are located also CompanyName.Tec hnologyName.
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.tec hnologyname/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 than prepending them with On as in
OnClose and OnClick?
The way it is now, I encounter a lot of naming conflicts/ambiguity when
trying to follow Microsoft's reccommened approach in naming my own events.
|
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 conversion
projects via DLL and P/Invoke: LAME (MP3 encoding), libsndfile (non-MP3
audio conversion), and libmad (MP3 decoding; through madlldlib).
Essentially, aumplib provides an OO wrapper to these libraries.
I am interested in any comments anyone...
|
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 variables
treated the same as parameters (i.e., camel case)?
I notice that Hungarian notation is being done away with.
Also, is it good practice to use an underscore to begin the name of a
field? I've seen that, and it seems like a good idea,...
|
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
system.drawing.dll", etc. However, in my Imports statements, I also use
Import System and Import System.Drawing, which I assume are 'namespaces'.
So, is it that Microsoft just wanted to confuse us by naming them the same,
or is there some direct...
|
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 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
| | |
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 a using and they specify the
namespace/type like MyNameSpace.MyNewType
Just curious. I'm leaning towards not using the using and specifying things
because then I know for a fact it's my datatype not a system datatype.
|
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 any comments.
--
|
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 recommended practise?
Thanks.
|
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
behind going for a different convention in .NET. The recommendations
do make sense (to me, at least but I may be wrong and would like
someone to correct me).
Scope Prefixes
Member Variable Prefix: Most of the people still use (and like the
idea...
|
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, people are often confused as to whether an ONU can Work As a Router. In this blog post, we’ll explore What is ONU, What Is Router, ONU & Router’s main usage, and What is the difference between ONU and Router. Let’s take a closer look !
Part I. Meaning of...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers, it seems that the internal comparison operator "<=>" tries to promote arguments from unsigned to signed.
This is as boiled down as I can make it.
Here is my compilation command:
g++-12 -std=c++20 -Wnarrowing bit_field.cpp
Here is the code in...
| | |
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven tapestry of website design and digital marketing. It's not merely about having a website; it's about crafting an immersive digital experience that captivates audiences and drives business growth.
The Art of Business Website Design
Your website is...
|
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing, and deployment—without human intervention. Imagine an AI that can take a project description, break it down, write the code, debug it, and then launch it, all on its own....
Now, this would greatly impact the work of software developers. The idea...
|
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM).
In this session, we are pleased to welcome a new presenter, Adolph Dupré who will be discussing some powerful techniques for using class modules.
He will explain when you may want to use classes instead of User Defined Types (UDT). For example, to manage the data in unbound forms.
Adolph will...
|
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one.
At the time of converting from word file to html my equations which are in the word document file was convert into image.
Globals.ThisAddIn.Application.ActiveDocument.Select();...
|
by: adsilva |
last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
|
by: muto222 |
last post by:
How can i add a mobile payment intergratation into php mysql website.
| | |
by: bsmnconsultancy |
last post by:
In today's digital era, a well-designed website is crucial for businesses looking to succeed. Whether you're a small business owner or a large corporation in Toronto, having a strong online presence can significantly impact your brand's success. BSMN Consultancy, a leader in Website Development in Toronto offers valuable insights into creating effective websites that not only look great but also perform exceptionally well. In this comprehensive...
| |
