Compiling internally instead of as a DLL?

H

Hugh Janus

Hi all,

I have added a class library project to my VB solution. All works fine
but when I compile the project, the compiler creates an external DLL
file. What I would rather it do is compile the class library project
into the main VB .exe app that I am compiling. Is this possible? If
so, how?

Thanks
 
P

Patrice

Either add the source (I believe there is also a "add as a link" feature
that allows all projects to refer to the same source file) or you'll likely
have to use the command line compiler that allows to compile source code
into "modules" that you can then combine when building the final exe...
 
H

Herfried K. Wagner [MVP]

Hugh Janus said:
I have added a class library project to my VB solution. All works fine
but when I compile the project, the compiler creates an external DLL
file. What I would rather it do is compile the class library project
into the main VB .exe app that I am compiling. Is this possible? If
so, how?

I do not see much sense in doing that because typically libraries are
intended to be reusable and replaceable. However, search for ILLink and
ILMerge on the Web...
 
P

Phill W.

Hugh said:
I have added a class library project to my VB solution. All works fine
but when I compile the project, the compiler creates an external DLL
file. What I would rather it do is compile the class library project
into the main VB .exe app that I am compiling. Is this possible? If
so, how?

If you build a library project, you get a library (Dll) out of it.

Move the class files into the main Executable's Project and it'll all
get built in together.

HTH,
Phill W.
 

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

Top