[MonoDevelop] Add-in questions & Assembly questions

Anirudh anirudh at anirudhsanjeev.org
Sat May 23 14:24:04 EDT 2009


I'm still a little shaky with trying to build an Addin to add a pad. I've
written the following basic addin:
http://github.com/ninjagod/TFAddin/tree/master but I'm not able to see
anything anywhere.

Can someone tell me which is the best way to make MonoDevelop recognize and
load my .dll file which is in extras/MonoDevelop.TaskForce/build/Debug

I've referenced locally built files, rather than those in the GAC.


On Tue, May 19, 2009 at 11:51 PM, Michael Hutchinson <
m.j.hutchinson at gmail.com> wrote:

> On Tue, May 19, 2009 at 1:28 PM, Anirudh <anirudh at anirudhsanjeev.org>
> wrote:
> > Hi.
> >
> > I think I figured the problem out, but not by changing the package
> configure
> > path, but by forcing the freshly compiled assemblies.
> >
> > I went to the references edit page for my particular project (which is in
> > main/addins) and changed the references to the MonoDevelop.Components.dll
> > and MonoDevelop.Ide.dll assemblies, which I had to browse and select. If
> I
> > tried loading the assemblies from the projects, there are only a few
> > projects displayed, lib libstetic and NUnitRunner, etc, but not the real
> > projects.
> >
> > At the end of the day, what was supposed to work worked. Moreover, it
> isn't
> > taking too long to compile which is good.
> >
> > So should I bother with the makefiles now or keep manually adding
> > assemblies?
> >
> > Also, are there any specific advantages towards keeping my stuff in
> extra/
> > rather than in main/Addins/...? I notice a significant slowdown on the
> > machine which I'm using when I use the full workspace, rather than an
> > individual solution.
> When we add your addin to MD SVN, it'll likely have to go in extras,
> but until then, if it makes things easier for you, it's fine to keep
> it in main/AddIns.
> The build system for extras is designed so each addin can distributed
> separately and built against an installed copy of MD (though the
> top-level configure script can hook them into the main build for
> convenience). This is useful for addins that are incomplete or
> unstable, or have a different release cycle from main MD, or bring in
> large dependencies.
> > Any suggestion on where to start for adding a new pad? Also I'll need to
> > have a look at some usage of the ExtensibleTreeView class.
> The ClassPad in IDE is an example of both. Other than that, there are
> pads everywhere -- for example, DesignerSupport's outline pad, or the
> debugger pads. IIRC AssemblyBrowser uses ExtensibleTreeView too.
> --
> Michael Hutchinson
> http://mjhutchinson.com

Fourth Year Undergraduate Student, Indian Institute of Technology, Kharagpur
E-Mail/jabber/googletalk: anirudh -at- anirudhsanjeev -dot- org
Phone: +91-97335-04828
My PGP key: anirudhsanjeev.org/pubkey.txt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/monodevelop-list/attachments/20090523/2a50051b/attachment-0001.html 

More information about the Monodevelop-list mailing list