[MonoDevelop] Monodevelop Addins

Michael Hutchinson m.j.hutchinson at gmail.com
Tue Jan 31 17:55:39 UTC 2012

On 29 January 2012 04:54, Ian Norton
<ian.norton-badrul at thales-esecurity.com> wrote:
> Hello All,
> I'm trying to work out the best way to add multiple version nunit support tot
> he nunit addin. I'm wondering what exactly this fragment of addin.xml means:
>    <Extension path="/MonoDevelop/Core/SupportPackages">
>        <Condition id="PackageNotInstalled" name="mono-nunit" version="2.7">
>            <Package name="nunit" version="2.4" clrVersion="Default">
>                <Assembly file="nunit.core.dll" />
>                <Assembly file="nunit.core.interfaces.dll" />
>                <Assembly file="nunit.framework.dll" />
>            </Package>
>        </Condition>
>    </Extension>
> Does this mean:
> If mono-nunit == 2.7 is not installed, create a pseudo package called nunit-2.4
> containing the nunit dlls shipped with monodevelop?

Pretty much, yes. I have no idea where the mono-unit package comes
from, however.

> To my mind the version 2.7 part looks like it is expecting it from mono 2.7, so
> what this looks like it does is "always" create an nunit package unless you
> have quite an old unstable mono install?
> I have a slight problem, that even if my project explicitly links against 2.5
> dlls, monodevelop forces it to use 2.4, could this be the cause?

I don't think so, but I I'm not sure I understand exactly what the
problem is. You mean that the test project (or the addin?) explicitly
references 2.5 but the build uses 2.4?

I've cc'd Dale because he was working on support for multiple test runners.

Michael Hutchinson

More information about the Monodevelop-list mailing list