ExamGuru IT/.Net Guru : C# File Includes on ASPFriends.com 'aspngcs' list

.NETGURU

C# File Includes

Messages

Related Types

This message was discovered on ASPFriends.com 'aspngcs' list.

Greg Bernhardt

I have a few files with constants that I want included in my web applications. How Do I include files in C#?

Greg Bernhardt
Forum Admin
http://www.physicsforums.com

Reply to this message...

Tim Musschoot

#using <namespacename>

where <namespacename> is the namespace defined in the file you wish to =
include. Also copy this file to the project directory.

----- Original Message -----
From: "Greg Bernhardt" <Click here to reveal e-mail address>
To: Click here to reveal e-mail address
Sent: Tue, 25 Jun 2002 04:13:23 -0500
Subject: C# File Includes
[Original message clipped]

Reply to this message...

Greg Bernhardt

how does this other file get compiled? is it a seperate dll then?
I'm usign VS.NET

thanks,
Greg
----- Original Message -----
From: "Tim Musschoot" <Click here to reveal e-mail address>
To: "aspngcs" <Click here to reveal e-mail address>
Sent: Tuesday, June 25, 2002 5:43 PM
Subject: [aspngcs] Re: C# File Includes

#using <namespacename>

where <namespacename> is the namespace defined in the file you wish to
include. Also copy this file to the project directory.

----- Original Message -----
From: "Greg Bernhardt" <Click here to reveal e-mail address>
To: Click here to reveal e-mail address
Sent: Tue, 25 Jun 2002 04:13:23 -0500
Subject: C# File Includes
[Original message clipped]

| [aspngcs] member Click here to reveal e-mail address = YOUR ID
| http://www.asplists.com/asplists/aspngcs.asp = JOIN/QUIT

Reply to this message...

Tim Musschoot

Nope. All source files are compiled into 1 DLL. If you want separate =
DLL's, make an new project and add the source files to it. Compile it =
into a DLL. In the first project, you'll have to add the DLL to the =
project. You include the classes with #using <namespacename> again...

----- Original Message -----
From: "Greg Bernhardt" <Click here to reveal e-mail address>
To: Click here to reveal e-mail address
Sent: Tue, 25 Jun 2002 05:54:22 -0500
Subject: Re: [aspngcs] Re: C# File Includes
[Original message clipped]

To: "aspngcs" <Click here to reveal e-mail address>
Sent: Tuesday, June 25, 2002 5:43 PM
Subject: [aspngcs] Re: C# File Includes
[Original message clipped]

To: Click here to reveal e-mail address
Sent: Tue, 25 Jun 2002 04:13:23 -0500
Subject: C# File Includes
[Original message clipped]

Reply to this message...

Robert Chartier

If you have more than one project, create a reference to the second PROJECT
(not its outputted DLL). Makes life easier because it ensures the
dependencies, etc...

Right click the project that needs to use the other, Add Reference...,
choose "Projects Tab" and double click the second project, and then hit OK.

/rob

At 07:06 PM 06/25/2002 -0400, you wrote:
[Original message clipped]

Robert Chartier
Author and Developer
604-975-5590
Click here to reveal e-mail address
http://www.aspalliance.com/nothingmn/

Reply to this message...

Greg Bernhardt

ok let me get this straight. I make a cs file with all my constants and
make them under a namespace. Then compile it with my project and it will be
included into my regular project dll. Then all I have to do is put the
"using whatever" as the namespace?

Greg
----- Original Message -----
From: "Robert Chartier" <Click here to reveal e-mail address>
To: "aspngcs" <Click here to reveal e-mail address>
Sent: Tuesday, June 25, 2002 6:15 PM
Subject: [aspngcs] Re: C# File Includes

[Original message clipped]

Reply to this message...

Greg Bernhardt

btw, when I import the namespace correctly, how do I access my constants?

Greg
----- Original Message -----
From: "Robert Chartier" <Click here to reveal e-mail address>
To: "aspngcs" <Click here to reveal e-mail address>
Sent: Tuesday, June 25, 2002 6:15 PM
Subject: [aspngcs] Re: C# File Includes

[Original message clipped]

Reply to this message...

Koen De Waele

Why the need for putting your constants in a separate dll?

Just put them in a public class, if necessary with a custom namespace
and put this class in his own source file (constants.cs).
Add this class file in al the projects who needs this file, but maintain
the class only in one space.
(I'm assuming you do have a version control system)

Something like this:

File constants.cs:
Namespace company.util
{
    public class CUtil
    {
        const string CONST1 = "number one";
        const string CONST2 = "number two";
        const string CONST3 = "number three";
        etc...
    }
}

Project A:

File projecta.cs
Namespace company.projecta
{
    using company.util;

    class CProjectA
    {
        string vara = Cutil.Const1;
        string varb = Cutil.Const2;
    }
}

Project B:

File projectb.cs:
Namespace company.projectb
{
    using company.util;

    class CProjectB
    {
        string vara = Cutil.Const2;
        string varb = Cutil.Const3;
    }
}

Note: if you use VS.net you have the added benefit of the intellisense
technology:
just type Cutil. and you have a list of the available constants.

My 2c,

Koen

[Original message clipped]

Reply to this message...

Andy Smith

aSdtIGdvaW5nIHRvIGd1ZXNzIHlvdSBhcmUgY29taW5nIGZyb20gVkJTY3JpcHQ/DQogDQp3aGF0
J3MgdGhlIGxhcmdlciBwaWN0dXJlIGhlcmU/IHdoYXQncyB0aGUgY29udGV4dD8NCg0KCS0tLS0t
T3JpZ2luYWwgTWVzc2FnZS0tLS0tIA0KCUZyb206IEdyZWcgQmVybmhhcmR0IFttYWlsdG86Z2hi
QHV3bS5lZHVdIA0KCVNlbnQ6IFR1ZSA2LzI1LzIwMDIgOToyMyBBTSANCglUbzogYXNwbmdjcyAN
CglDYzogDQoJU3ViamVjdDogW2FzcG5nY3NdIFJlOiBDIyBGaWxlIEluY2x1ZGVzDQoJDQoJDQoN
CglidHcsIHdoZW4gSSBpbXBvcnQgdGhlIG5hbWVzcGFjZSBjb3JyZWN0bHksIGhvdyBkbyBJIGFj
Y2VzcyBteSBjb25zdGFudHM/DQoJDQoJR3JlZw0KCS0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0t
LS0NCglGcm9tOiAiUm9iZXJ0IENoYXJ0aWVyIiA8cmNoYXJ0aWVyaEBhc3BmcmVlLmNvbT4NCglU
bzogImFzcG5nY3MiIDxhc3BuZ2NzQGFzcGZyaWVuZHMuY29tPg0KCVNlbnQ6IFR1ZXNkYXksIEp1
bmUgMjUsIDIwMDIgNjoxNSBQTQ0KCVN1YmplY3Q6IFthc3BuZ2NzXSBSZTogQyMgRmlsZSBJbmNs
dWRlcw0KCQ0KCQ0KCT4NCgk+IElmIHlvdSBoYXZlIG1vcmUgdGhhbiBvbmUgcHJvamVjdCwgY3Jl
YXRlIGEgcmVmZXJlbmNlIHRvIHRoZSBzZWNvbmQNCglQUk9KRUNUDQoJPiAobm90IGl0cyBvdXRw
dXR0ZWQgRExMKS4gIE1ha2VzIGxpZmUgZWFzaWVyIGJlY2F1c2UgaXQgZW5zdXJlcyB0aGUNCgk+
IGRlcGVuZGVuY2llcywgZXRjLi4uDQoJPg0KCT4gUmlnaHQgY2xpY2sgdGhlIHByb2plY3QgdGhh
dCBuZWVkcyB0byB1c2UgdGhlIG90aGVyLCBBZGQgUmVmZXJlbmNlLi4uLA0KCT4gY2hvb3NlICJQ
cm9qZWN0cyBUYWIiIGFuZCBkb3VibGUgY2xpY2sgdGhlIHNlY29uZCBwcm9qZWN0LCBhbmQgdGhl
biBoaXQNCglPSy4NCgk+DQoJPiAvcm9iDQoJPg0KCT4NCgk+IEF0IDA3OjA2IFBNIDA2LzI1LzIw
MDIgLTA0MDAsIHlvdSB3cm90ZToNCgk+ID5Ob3BlLiAgQWxsIHNvdXJjZSBmaWxlcyBhcmUgY29t
cGlsZWQgaW50byAxIERMTC4gIElmIHlvdSB3YW50IHNlcGFyYXRlDQoJPiA+RExMJ3MsIG1ha2Ug
YW4gbmV3IHByb2plY3QgYW5kIGFkZCB0aGUgc291cmNlIGZpbGVzIHRvIGl0LiAgQ29tcGlsZSBp
dA0KCT4gPmludG8gYSBETEwuICBJbiB0aGUgZmlyc3QgcHJvamVjdCwgeW91J2xsIGhhdmUgdG8g
YWRkIHRoZSBETEwgdG8gdGhlDQoJPiA+cHJvamVjdC4gIFlvdSBpbmNsdWRlIHRoZSBjbGFzc2Vz
IHdpdGggI3VzaW5nIDxuYW1lc3BhY2VuYW1lPiBhZ2Fpbi4uLg0KCT4gPg0KCT4gPi0tLS0tIE9y
aWdpbmFsIE1lc3NhZ2UgLS0tLS0NCgk+ID5Gcm9tOiAiR3JlZyBCZXJuaGFyZHQiIDxnaGJAdXdt
LmVkdT4NCgk+ID5UbzogYXNwbmdjc0Bhc3BmcmllbmRzLmNvbQ0KCT4gPlNlbnQ6IFR1ZSwgMjUg
SnVuIDIwMDIgMDU6NTQ6MjIgLTA1MDANCgk+ID5TdWJqZWN0OiBSZTogW2FzcG5nY3NdIFJlOiBD
IyBGaWxlIEluY2x1ZGVzDQoJPiA+ID4NCgk+ID4gPmhvdyBkb2VzIHRoaXMgb3RoZXIgZmlsZSBn
ZXQgY29tcGlsZWQ/ICBpcyBpdCBhIHNlcGVyYXRlIGRsbCB0aGVuPw0KCT4gPiA+SSdtIHVzaWdu
IFZTLk5FVA0KCT4gPiA+DQoJPiA+ID50aGFua3MsDQoJPiA+ID5HcmVnDQoJPiA+ID4tLS0tLSBP
cmlnaW5hbCBNZXNzYWdlIC0tLS0tDQoJPiA+RnJvbTogIlRpbSBNdXNzY2hvb3QiIDxUaW0uTXVz
c2Nob290QHJ1Zy5hYy5iZT4NCgk+ID5UbzogImFzcG5nY3MiIDxhc3BuZ2NzQGFzcGZyaWVuZHMu
Y29tPg0KCT4gPlNlbnQ6IFR1ZXNkYXksIEp1bmUgMjUsIDIwMDIgNTo0MyBQTQ0KCT4gPlN1Ympl
Y3Q6IFthc3BuZ2NzXSBSZTogQyMgRmlsZSBJbmNsdWRlcw0KCT4gPiA+DQoJPiA+ID4NCgk+ID4g
PiN1c2luZyA8bmFtZXNwYWNlbmFtZT4NCgk+ID4gPg0KCT4gPiA+d2hlcmUgPG5hbWVzcGFjZW5h
bWU+IGlzIHRoZSBuYW1lc3BhY2UgZGVmaW5lZCBpbiB0aGUgZmlsZSB5b3Ugd2lzaCB0bw0KCT4g
PiA+aW5jbHVkZS4gIEFsc28gY29weSB0aGlzIGZpbGUgdG8gdGhlIHByb2plY3QgZGlyZWN0b3J5
Lg0KCT4gPiA+DQoJPiA+ID4tLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tDQoJPiA+RnJvbTog
IkdyZWcgQmVybmhhcmR0IiA8Z2hiQHV3bS5lZHU+DQoJPiA+VG86IGFzcG5nY3NAYXNwZnJpZW5k
cy5jb20NCgk+ID5TZW50OiBUdWUsIDI1IEp1biAyMDAyIDA0OjEzOjIzIC0wNTAwDQoJPiA+U3Vi
amVjdDogQyMgRmlsZSBJbmNsdWRlcw0KCT4gPiA+Pg0KCT4gPiA+PkkgaGF2ZSBhIGZldyBmaWxl
cyB3aXRoIGNvbnN0YW50cyB0aGF0IEkgd2FudCBpbmNsdWRlZCBpbiBteSB3ZWINCgk+ID4gPj1w
cGxpY2F0aW9ucy4gIEhvdyBEbyBJIGluY2x1ZGUgZmlsZXMgaW4gQyM/DQoJPiA+ID4+DQoJPiA+
ID4+R3JlZyBCZXJuaGFyZHQNCgk+ID4gPj5Gb3J1bSBBZG1pbg0KCT4gPiA+Pmh0dHA6Ly93d3cu
cGh5c2ljc2ZvcnVtcy5jb20NCgk+ID4gPj4NCgk+ID4gPg0KCT4gPiA+fCBbYXNwbmdjc10gbWVt
YmVyIGdoYkB1d20uZWR1ID0gWU9VUiBJRA0KCT4gPiA+fCBodHRwOi8vd3d3LmFzcGxpc3RzLmNv
bS9hc3BsaXN0cy9hc3BuZ2NzLmFzcCA9IEpPSU4vUVVJVA0KCT4gPiA+DQoJPiA+DQoJPiA+fCBb
YXNwbmdjc10gbWVtYmVyIHJjaGFydGllcmhAYXNwZnJlZS5jb20gPSBZT1VSIElEDQoJPiA+fCBo
dHRwOi8vd3d3LmFzcGxpc3RzLmNvbS9hc3BsaXN0cy9hc3BuZ2NzLmFzcCA9IEpPSU4vUVVJVA0K
CT4NCgk+DQoJPiBSb2JlcnQgQ2hhcnRpZXINCgk+IEF1dGhvciBhbmQgRGV2ZWxvcGVyDQoJPiA2
MDQtOTc1LTU1OTANCgk+IHJvYkBhc3BmcmVlLmNvbQ0KCT4gaHR0cDovL3d3dy5hc3BhbGxpYW5j
ZS5jb20vbm90aGluZ21uLw0KCT4NCgk+DQoJPiB8IFthc3BuZ2NzXSBtZW1iZXIgZ2hiQHV3bS5l
ZHUgPSBZT1VSIElEDQoJPiB8IGh0dHA6Ly93d3cuYXNwbGlzdHMuY29tL2FzcGxpc3RzL2FzcG5n
Y3MuYXNwID0gSk9JTi9RVUlUDQoJPg0KCT4NCgkNCgkNCgl8IFthc3BuZ2NzXSBtZW1iZXIgQW5k
eS5TbWl0aEBtYWN0ZWMuY29tID0gWU9VUiBJRA0KCXwgaHR0cDovL3d3dy5hc3BsaXN0cy5jb20v
YXNwbGlzdHMvYXNwbmdjcy5hc3AgPSBKT0lOL1FVSVQNCgkNCg0K

Reply to this message...

TIM ELLISON

Ex:
Namespace Foo.Bar
{
    Public class AnotherClass
    {
        public const int WM_INS_FIELD = 0;
        public static const int WM_OUT_FIELD = 1;

    }
}

// and in other project.
using Foo.Bar;
namespace Bar.Foo
{
    public class ThisClass
    {
        public ThisClass()
        {
            // reference to static constant,
            // no need to construct class.
            int outField = Foo.Bar.AnotherClass.WM_OUT_FIELD;

            // need to construct to get this one.
            AnotherClass a = new AnotherClass();
            int infield = a.WM_INS_FIELD;
        }
    }
}

Regards,

Tim Ellison
Senior Web Applications Developer,
Long and Foster Real Estate
703-359-1884
Click here to reveal e-mail address

-----Original Message-----
From: Greg Bernhardt [mailto:Click here to reveal e-mail address]
Sent: Tuesday, June 25, 2002 11:23 AM
To: aspngcs
Subject: [aspngcs] Re: C# File Includes

btw, when I import the namespace correctly, how do I access my constants?

Greg
----- Original Message -----
From: "Robert Chartier" <Click here to reveal e-mail address>
To: "aspngcs" <Click here to reveal e-mail address>
Sent: Tuesday, June 25, 2002 6:15 PM
Subject: [aspngcs] Re: C# File Includes

[Original message clipped]

| [aspngcs] member Click here to reveal e-mail address = YOUR ID
| http://www.asplists.com/asplists/aspngcs.asp = JOIN/QUIT

Reply to this message...

Stewart Haddock

You will also want to look into setting constants on the web.config file for
global variables such as the 'dsn' or the admin email address.

example
-------------
<appSettings>
<add key="dsn" value="localhost;uid=MyUserName;pwd=;" />
<add key="msmqserver" value="server\myqueue" />
</appSettings>
------------

check out.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/htm
l/cpconformatofconfigurationfiles.asp

To access them.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/htm
l/cpconformatofconfigurationfiles.asp

Thanks
Stewart

-----Original Message-----
From: Koen De Waele [mailto:Click here to reveal e-mail address]
Sent: Wednesday, June 26, 2002 4:53 AM
To: aspngcs
Subject: [aspngcs] Re: C# File Includes

Why the need for putting your constants in a separate dll?

Just put them in a public class, if necessary with a custom namespace
and put this class in his own source file (constants.cs).
Add this class file in al the projects who needs this file, but maintain
the class only in one space.
(I'm assuming you do have a version control system)

Something like this:

File constants.cs:
Namespace company.util
{
    public class CUtil
    {
        const string CONST1 = "number one";
        const string CONST2 = "number two";
        const string CONST3 = "number three";
        etc...
    }
}

Project A:

File projecta.cs
Namespace company.projecta
{
    using company.util;

    class CProjectA
    {
        string vara = Cutil.Const1;
        string varb = Cutil.Const2;
    }
}

Project B:

File projectb.cs:
Namespace company.projectb
{
    using company.util;

    class CProjectB
    {
        string vara = Cutil.Const2;
        string varb = Cutil.Const3;
    }
}

Note: if you use VS.net you have the added benefit of the intellisense
technology:
just type Cutil. and you have a list of the available constants.

My 2c,

Koen

[Original message clipped]

| [aspngcs] member Click here to reveal e-mail address = YOUR ID
| http://www.asplists.com/asplists/aspngcs.asp = JOIN/QUIT

Reply to this message...

ghb@uwm.edu

Thanks for the tip stewart, I am using that connection tip. However, I have a
list of 50 or so constants that I need to use across 5 or 6 projects. Thats
why I need a seperate dll. btw, for all my projects in VS.NET, can I dump all
my dlls in one bin, but then seperate my projects into folders containing the
aspx files. Let me give you an example:

ROOT:
web.config
global.asax
/bin
all project dlls plus constant dll
/projects
/claims
claims web form
/checks
checks web form
/admin
admin web form

does this make sense? So that I don't need a bin for every project. Does this
work?

Quoting Stewart Haddock <Click here to reveal e-mail address>:

[Original message clipped]

Reply to this message...

Daniel Wilson

Greg,

This is from Tim earlier in this thread.
Ex:
Namespace Foo.Bar
{
    Public class AnotherClass
    {
        public const int WM_INS_FIELD = 0;
        public static const int WM_OUT_FIELD = 1;

    }
}

// and in other project.
using Foo.Bar;
namespace Bar.Foo
{
    public class ThisClass
    {
        public ThisClass()
        {
            // reference to static constant,
            // no need to construct class.
            int outField = Foo.Bar.AnotherClass.WM_OUT_FIELD;

            // need to construct to get this one.
            AnotherClass a = new AnotherClass();
            int infield = a.WM_INS_FIELD;
        }
    }
}

As you can see it depends upon whether or constants are static or not.

-Daniel Wilson

-----Original Message-----
From: Greg Bernhardt [mailto:Click here to reveal e-mail address]
Sent: Tuesday, June 25, 2002 11:23 AM
To: aspngcs
Subject: [aspngcs] Re: C# File Includes

btw, when I import the namespace correctly, how do I access my constants?

Greg
----- Original Message -----
From: "Robert Chartier" <Click here to reveal e-mail address>
To: "aspngcs" <Click here to reveal e-mail address>
Sent: Tuesday, June 25, 2002 6:15 PM
Subject: [aspngcs] Re: C# File Includes

[Original message clipped]

| [aspngcs] member Click here to reveal e-mail address = YOUR ID
| http://www.asplists.com/asplists/aspngcs.asp = JOIN/QUIT

Reply to this message...

System.Security.Cryptography.Xml.Reference

ExamGuru IT Solutions - .Net Guru is owned and operated by ExamGuru, Inc., the man behind .Net Guru. If you're in the market for bespoke software or software consultancy, why not get him and his highly trained team to help? - www.examguru.net/ITCertification

Need Dot Net Interview Questions?
Ask ExamGuru, Inc. for advice and help on Passing .Net Interviews

.Net Projects
Best-of-breed application framework for .NET projects, developed by ExamGuru, Inc. and ExamGuru IT

Free .net Help
Commission ExamGuru, Inc. and his team for your next bespoke software project

FogBUGZ
The only bug tracking system carefully crafted with one goal in mind: helping teams create great software.

Awesome Tools
If you don't know about these, you're missing out... IT Certification Questions
IT Interview Questions
Free Oracle 10g Training
MCSE Boortcamp
Cisco Study Guides
Cheap Study Guides
Exact Questions
Dot Net Interview Questions
Oracle OCP
Cheap Travel
Designer Perfumes - Wholesale Prices
Free Programming Tutorials

	Copyright © ExamGuru, Inc. 2001-2006
	Contact Us - Terms of Use - Privacy Policy - www.dot-net-guru.com - www.examguru.net - www.oraclesource.net - www.itinterviews.net - www.examguru.net/ITCertification