Picture 3 libraries each with 200 functions of which I only want to
use 1 from each of the libraries.

I would prefer not copy the entire DLL into every project.  It would
be much better to simply include the source code in the current
project.  This problem increases exponentially as multiple versions of
the libraries are developed/deployed.  This will happen a lot during
the first year.

During development it is much easier to directly edit the linked
source file rather than add dependant sub-projects.

The compiler will optimize linked sources.

A single optimized EXE is quicker and easier to deploy.

I don't need to concern my self with version issues.

The runtime dependency map is simpler (there is none).

You avoid the runtime penalty of dynamically loading/linking
libraries.

It is trivial to create a snapshot of the few classes that a project is
using.

Come to think of it...why would you use a Class Library? :)

Cheers...David

----- Original Message -----
From: "Shawn Wildermuth" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 22, 2002 5:14 PM
Subject: Re: [DOTNET] How to create a C# source lib?


I don't think this is really what you want, but there isn't a C# library
kind of thing.  If you create a Class Library, it will create an
assembly you can create a reference to, but that will still be linked
in.

Why not just create a Class Library?

Thanks,

Shawn Wildermuth
[EMAIL PROTECTED]

> -----Original Message-----
> From: dotnet discussion [mailto:[EMAIL PROTECTED]]
> On Behalf Of David Ferguson
> Sent: Wednesday, May 22, 2002 5:17 PM
> To: [EMAIL PROTECTED]
> Subject: [DOTNET] How to create a C# source lib?
>
>
> How to create a C# source lib?
>
> I would like to start C# a source code library.  It will
> include general utility classes.  I will keep the library in
> one central place, say \dev\srclib.  I will add individual
> files to projects as needed.
>
> Here is the problem...
>
> When 'I use Project/Add Existing Item' to include the source
> module VS.NET makes a copy of the source file in the current
> project directory.  Obviously any changes made to this copy
> don't make it back to original source.
>
> So I how do get VS.NET to create a reference and not make a copy?
>
> Thanks...David
>
> You can read messages from the DOTNET archive, unsubscribe
> from DOTNET, or subscribe to other DevelopMentor lists at
> http://discuss.develop.com.
>

You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

Reply via email to