stupid question

  • Thread starter Thread starter ilker
  • Start date Start date
I

ilker

I developing my own application.

I Just wandering, do I import some extra .net class library dll files into
my exe (project) ?
 
ilker said:
I developing my own application.

I Just wandering, do I import some extra .net class library dll files into
my exe (project) ?

For a basic .Net application you only need to reference mscorlib.dll,
which is normally referenced by default, and you will usually want to import
the System namespace by means of a "using" directive.
You only have to reference additional .Net libraries if you are going to
use them. For example, if you plan to use GDI+ to draw graphics, you will
need to reference system.drawing.dll (and you will probably want import the
System.Drawing namespace with a "using" directive). It all depends on the
kind of application that you are writing and the functionality that you wish
to use from the libraries.
 
ilker,

You have different ways to do that, two of those

Either you set the project that created the DLL into your solution and use
Project -> references and add the project to your main (startup) project.
This is usefull as you are still busy with the DLL.

Either you choose in the Solution Explorer the DLL using the browsing option
to add it to your main Project (as it is a DLL that you are not updating
anymore).

The two ways of using Project of References in the Solution explorer are in
both situations usable.

Don't forget to set the using clause in your startup project.

Cor
 
sorry for my bad engish :)
I think I can't explain exactly

I want to Import (merge) external (3th party) .net class library dll files
into my project cause I don't want to deliver any extra files but mine
executables
 
I developing my own application.

I Just wandering, do I import some extra .net class library dll files into
my exe (project) ?

If you aren't implementing some stuff beyond native .NET assemblies,
usually you don't have to. However there are extra classes or
components which can be seen when you click on "choose items" in
toolbox either "add reference" in your solution. (Winform)

And sure, if you're using external .NET assemblies written by 3rd
party companies, you need to add reference plus add "using" directive
in order to make them work at project-level.

Hope this helps,

Onur Güzel
 
ilker said:
sorry for my bad engish :)
I think I can't explain exactly

I want to Import (merge) external (3th party) .net class library dll files
into my project cause I don't want to deliver any extra files but mine
executables

That's a recipe for extra maintenance in the long run, and may not even
be allowed by the 3rd party licence, but ILMerge might help you if you
really decide to go ahead with it.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top