By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,581 Members | 1,811 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,581 IT Pros & Developers. It's quick & easy.

EXE vs DLL Creation

P: n/a
Hello all,

In Clarion for Windows we were able to create many DLL's and a single
execute that would link in the DLL's (LIB's). You could cross DLL->DLL
(imports/exports) and interconnect many procedures/methods. So we could
create a DLL for Persons, one for Businesses, and so on.

What is the recommended way to do this in VB.NET 2005? I would rather not
compile the same Class Library or Module into many EXE's and bloat the
system. Is there anyway to accomplish the same thing or something similar
in VB.NET? I have not seen any project settings to compile anything into
just a DLL.

Any help would be greatly appreciated.

Ben Kim
Emergitech
Feb 7 '06 #1
Share this Question
Share on Google+
6 Replies


P: n/a
If you create a Class Library project, it will compile into a .dll
which can be used by many .exe's or .dll's. I'm not sure what your
concern is? If the assemblies (.dlls) you create are to be shared by
many different apps, they can be installed in the Global Assembly Cache
(GAC) so that only a single copy of the .dll exists on the system.

Feb 7 '06 #2

P: n/a
Ben,

A very classic way, not the way it is done anymore in Net in my opinion.

(Your method is a classic way of using memory in a single user 640Kb
environment)

However this is my opinion.

Cor
Feb 7 '06 #3

P: n/a
Cor,

Remember I am coming from a Clarion environment which creates 32-bit DLL's
and EXE's. So if that is the classic way, what is the "DOT NET" way?

Ben Kim
Emergitech

"Cor Ligthert [MVP]" <no************@planet.nl> wrote in message
news:uZ**************@TK2MSFTNGP14.phx.gbl...
Ben,

A very classic way, not the way it is done anymore in Net in my opinion.

(Your method is a classic way of using memory in a single user 640Kb
environment)

However this is my opinion.

Cor

Feb 7 '06 #4

P: n/a
Create a project that is a Class Library. That compiles into a DLL.

This is in fact the recommended way. All common functionality goes into a
DLL. Then multiple applications can reference the same DLL and use it,
without having their own copy of the same code.

The Global Assembly Cache (GAC) is also there, so that not only do you only
have 1 copy of the code on your development machine, but now you can have
only 1 copy of the DLL on a deployment machine, but have multiple
applications all use that one copy.

You might want to do some searching of the .net framework documentation and
the web for more details on this.

"Ben Kim" <bk**@NOSPAMemergitech.com> wrote in message
news:OZ**************@TK2MSFTNGP14.phx.gbl...
Hello all,

In Clarion for Windows we were able to create many DLL's and a single
execute that would link in the DLL's (LIB's). You could cross DLL->DLL
(imports/exports) and interconnect many procedures/methods. So we could
create a DLL for Persons, one for Businesses, and so on.

What is the recommended way to do this in VB.NET 2005? I would rather not
compile the same Class Library or Module into many EXE's and bloat the
system. Is there anyway to accomplish the same thing or something similar
in VB.NET? I have not seen any project settings to compile anything into
just a DLL.

Any help would be greatly appreciated.

Ben Kim
Emergitech

Feb 7 '06 #5

P: n/a
Ben,

Remember I am coming from a Clarion environment which creates 32-bit DLL's
and EXE's. So if that is the classic way, what is the "DOT NET" way?

Not to care about it before it is needed and folow the tools in the way as
they make your program.

You can create as much class librarys as you want by the way to make those
librarys reusable.

Cor
Feb 7 '06 #6

P: n/a
Excellent. That is what I needed to know.

Thank you.
"Marina Levit [MVP]" <so*****@nospam.com> wrote in message
news:e%***************@TK2MSFTNGP14.phx.gbl...
Create a project that is a Class Library. That compiles into a DLL.

This is in fact the recommended way. All common functionality goes into a
DLL. Then multiple applications can reference the same DLL and use it,
without having their own copy of the same code.

The Global Assembly Cache (GAC) is also there, so that not only do you
only have 1 copy of the code on your development machine, but now you can
have only 1 copy of the DLL on a deployment machine, but have multiple
applications all use that one copy.

You might want to do some searching of the .net framework documentation
and the web for more details on this.

"Ben Kim" <bk**@NOSPAMemergitech.com> wrote in message
news:OZ**************@TK2MSFTNGP14.phx.gbl...
Hello all,

In Clarion for Windows we were able to create many DLL's and a single
execute that would link in the DLL's (LIB's). You could cross DLL->DLL
(imports/exports) and interconnect many procedures/methods. So we could
create a DLL for Persons, one for Businesses, and so on.

What is the recommended way to do this in VB.NET 2005? I would rather
not compile the same Class Library or Module into many EXE's and bloat
the system. Is there anyway to accomplish the same thing or something
similar in VB.NET? I have not seen any project settings to compile
anything into just a DLL.

Any help would be greatly appreciated.

Ben Kim
Emergitech


Feb 7 '06 #7

This discussion thread is closed

Replies have been disabled for this discussion.