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.
Are you using SVN or GIT? Which command are you using for committing?
I right-click and choose Version Control / Commit
The problem here is that SVN commands are per-folder. When you run the commit code in the MyApp solution, the SVN commit command is run on the folder that contains the solution. Since AnotherApp is outside the solution folder, it is ignored.
A solution to this problem is to change the file location directory in the solution. To do it, open the solution properties, in the Main Settings section, click on Location of Project Files. In the Root Directory entry select the parent folder of the solution. After doing that, a commit of the solution should include changes done in the sibling library (although it will include changes in all other projects under the same folder).
This is not only about committing, but also about all other version control operations. Also this may be a problem inside a project, when a project references files which are outside the project directory. We may consider other solutions, although I fear they will not be easy to implement using the current version control infrastructure.
Thank you for the info. What I would hope/expect when performing an operation at the solution level (top node) is that it operate against its own node and then tell each project within the solution to operate at its level. This way no matter where the project resided on disk the project would take care of itself.