Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
I built a MD addin that depends on some external assembly, like MonoDevelop.VersionControl.Git.dll depends on NGit.dll.
Now, I tried to create a .mpack package using "mdtool setup pack" command. It resulted in an archive that does not contain the dependencies.
- https://dl.dropbox.com/u/493047/2012/07/MonoDevelop.VersionControl.Mercurial.dll (the addin)
- https://dl.dropbox.com/u/493047/2012/07/Mercurial.Net.dll (dep)
In case you want to build those assemblies, the sources are in my MD fork:
With bug #3700 (mdtool gsetup never works), there is not really a way to build a working mpack at all.
Mono.Addins has no way to know whether you are supplying the dll or expecting it to come from some other addin or from the GAC. You must declare the dependency in the <Runtime> element:
<Import assembly="Mercurial.Net.dll "/>
Note you don't need to explicitly Import on MonoDevelop.VersionControl.Mercurial.dll, it's implicitly imported if the addin manifest is embedded into it.
I don't think that works or in the way we (addin devs) expect. I replaced the <Runtime> element and now it looks like:
<Import assembly="Mercurial.Net.dll" />
Then I rebuilt it (to have it bundled in my addin dll), and went to main/build/AddIns/VersionControl, and ran "mdtool setup pack MonoDevelop.VersionControl.Mercurial.dll" . The resulting .mpack still does not contain Mercurial.Net.dll.
Or if you meant that the mpack won't contain any dependencies because Mono.Addins has no way to know the origin of the assembly, how can I distribute the addin that *actually* works, with incomplete dependencies?
That should work, are you sure the resource got picked up? Try rebuilding.
Somehow I needed some updates to the build and now it worked! Thanks.