Share common code

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Calvin KD - 27 Sep 2004 06:49 GMT

I'm a newbie to Dot NET. Can anyone show me how to compile a reusable code
repository so that codes can be reused by a number of Web Forms in the .NET
Framework. In the classic ASP, Include files are used but I don't know how to
do it in C#.Net.

Any help is greatly appreciated.

Reply to this Message

Richard Blewett [DevelopMentor] - 27 Sep 2004 07:39 GMT

From within Visual Studio:

Create a "Class Library" Project and put your common code in there. Be sure to mark all the classes that wou want visible as public. Set a reference to this project from the applications that want to use the common code.

From the command line:

Put roud classes in one or more .cs files making sure to mark all the necessary exposed classes as public then run
csc /t:library *.cs
to create a .dll. This then needs to be referenced by the applications using the common code

Regards

Richard Blewett - DevelopMentor
http://staff.develop.com/richardb/weblog

nntp://news.microsoft.com/microsoft.public.dotnet.framework/<97F75292-54D0-48BF-99F8-5D455A8FDBE9@microsoft.com>

I'm a newbie to Dot NET. Can anyone show me how to compile a reusable code
repository so that codes can be reused by a number of Web Forms in the .NET
Framework. In the classic ASP, Include files are used but I don't know how to
do it in C#.Net.

Any help is greatly appreciated.

[microsoft.public.dotnet.framework]

Reply to this Message

Calvin KD - 27 Sep 2004 08:19 GMT

Thanks Richard.
Will those dlls automatically be part of the .NET application at deployment
(packaged) or do you have to administer them separately on the Server?

I'm using Visual Studio 2003 with DotNET version 1.1

> From within Visual Studio:
>
[quoted text clipped - 27 lines]
>
> [microsoft.public.dotnet.framework]

Reply to this Message

Richard Blewett [DevelopMentor] - 27 Sep 2004 08:27 GMT

If you build the MSI using VS.NET then yes, they wikll be part of the deployment package.

The only issue you may get is that you will end up with multiple copies of the shared assembly - one for each application. This is not necessarily a problem. If you only want one copy you will have to install the shared assembly in the GAC which means strong naming it.

Regards

Richard Blewett - DevelopMentor
http://staff.develop.com/richardb/weblog

nntp://news.microsoft.com/microsoft.public.dotnet.framework/<11C4382B-C697-4D45-A156-04BFA8854D03@microsoft.com>

Thanks Richard.
Will those dlls automatically be part of the .NET application at deployment
(packaged) or do you have to administer them separately on the Server?

I'm using Visual Studio 2003 with DotNET version 1.1

"Richard Blewett [DevelopMentor]" wrote:

> From within Visual Studio:
>
[quoted text clipped - 26 lines]
>
> [microsoft.public.dotnet.framework]

[microsoft.public.dotnet.framework]

Reply to this Message

Calvin KD - 27 Sep 2004 08:53 GMT

That's OK.
Thanks Richard.

> If you build the MSI using VS.NET then yes, they wikll be part of the deployment package.
>
[quoted text clipped - 56 lines]
>
> [microsoft.public.dotnet.framework]

Reply to this Message

Share common code

Free Magazines