[MonoDevelop] Include one projects DLL's into another

[Greg Zapp]

[Off-list reply]
Hello and thank you for your help. I think this has me started down a
usable path.  I'm setting it's output to be at
"bin\$(Configuration)\Plugins" on the main project.  Unfortunately I'm
referencing the main project from the plugins project and this appears to
be causing it to build the main project and toss it in the "Plugins"
directory as well.  I'm referencing the main project because I'm injecting
an object into the plugins so I suspect building the main project is
necessary, it's just not ideal for it to be included in the output with the
library DLL's I'm building.  Am I approaching this a poor way, or is this a
job for custom commands?

[Follow up]
I found an answer to my own question :)  I disabled local copy on the
reference properties and this prevents them from being copies to the output
directory.  I think I'm on my way but I'd be happy for any further pointers
should anybody still be reading this and have some solid tips.

Thanks Again,
   -Greg


On Mon, Oct 7, 2013 at 9:52 PM, Eberhard Beilharz <eb1 at sil.org> wrote:

> What about changing the output path of the plugins (in the options of
> the project under Build/Output) to the directory where the main project
> builds?
>
>     Eberhard
>
> Rapzid wrote on 2013-10-07 at 09:31 +0200:
>
>
> > Hello,
> >
> > I'm starting to get into needing to setup a solution a bit more
> complicated
> > than in the past and I could use some advice.  My .net service's
> > functionality will mostly be provided by plugins.  I'm a bit new to this
> > workflow and am unsure how to approach developing the main project and
> the
> > plugins project efficiently.  I would like the DLL's built from the
> plugins
> > project to be included in the output directory of the main project so
> that
> > it can  load the assemblies and instantiate any plugins it finds in some
> > namespace(like "Project.Plugins").  Unfortunately I have no idea how to
> go
> > about setting this sort of thing up in mono develop.  Any advice would be
> > much appreciate.
> >
> >
> > Thanks,
> >    Greg
> >
> >
> >
> > --
> > View this message in context:
> http://mono.1490590.n4.nabble.com/Include-one-projects-DLL-s-into-another-tp4661046.html
> > Sent from the Mono - MonoDevelop IDE mailing list archive at Nabble.com.
> > _______________________________________________
> > Monodevelop-list mailing list
> > Monodevelop-list at lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/monodevelop-list
>
> _______________________________________________
> Monodevelop-list mailing list
> Monodevelop-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/monodevelop-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/monodevelop-list/attachments/20131007/3b1e860b/attachment.html>