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 for Bug 3232 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
A typical use of submodules is to pull in an external project so you can add it to your solution and build it. Unfortuantely by default "git clone foo" does not checkout out submodules. There is also no UI in monodevelop to check them out manually. The only way to build a project such as this is to manually open a terminal and execute the required git commands to check out the various submodules.
We have a few things to worry about:
1) A fresh clone of a repository from within monodevelop
2) Opening existing repositories which have not had their submodules checked out
3) Opening existing repositories with stale submodule checkouts (ones which need updating)
4) Updating a repository has updated the submodule ref.
1) We can automatically check out any submodules as part of doing a clone. Alternatively when cloning a repository we could have a checkbox saying "Check out submodules too?" and have it checked by default
2) When opening a solution the first step could be to check for submodules and then prompt the user "Hey, do you want to check out these submodules as they might be required for the project"
3) Same as for 2.
4) When a git pull/fetch has been executed and a submodule has been added/removed/modified we could prompt the user to re-sync the submodule right after the pull/fetch finishes.
1) is fixed with #353.
2), 3) are a bit of a problem. We don't know where to hook the submodule init.
4) is pretty hard to do properly. We have no way to be notified of remote changes on that module (except timed checks).