If you have the source for both dlls you could place them in the same
project and compile them together. You would not necessarily need to have
the class files in the same directory as the project as you can always
"link" to the files instead. Or you could use the ILMerge utility to merge
two assemblies together
(
http://research.microsoft.com/~mbarnett/ilmerge.aspx). I haven't used this
utility but it should allow you to merge your two dlls together after they
have been compiled. Is it really that big of a problem to distribute two
assemblies? It may allow for cleaner separation in the long run to keep the
utilities assembly and a custom control assembly separate. When the devs
drag and drop an instance of a custom control from the toolbox the design
environment should add a reference to the custom control assembly as well as
its dependencies.
--
Tim Wilson
..Net Compact Framework MVP
[quoted text, click to view] <chambersdon@hotmail.com> wrote in message
news:1120148888.026910.276050@g14g2000cwa.googlegroups.com...
> I have several projects that I need to compile into a single DLL. Is
> this possible?
>
> We have a project called 'Utilities' that includes classes to which
> encapsulate business logic.
> I've now created another project called 'Controls' with custom controls
> that can be used by all of our developers. The Controls project has a
> reference to the Utilites project because it needs some of this
> functionality.
> How can I build the Controls project so everything needed is put into a
> single dll?
>
> A single dll will make it much easier to manage and simplier to keep
> each developers environemnt up to date. Any new developer wuld just
> need the out-of-box IDE and one DLL to access our custom controls.
> Can the IDE build a single DLL like the old C++ visual studio IDE could
> do? I think this was called a 'static dll'. If not, can any of the
> command line line tools give me what I need?
>
> Thanks,
> Don
>