Bug 879 - Update from SVN on solution does not update all sub projects
Summary: Update from SVN on solution does not update all sub projects
Status: RESOLVED NOT_ON_ROADMAP
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Version Control ()
Version: 2.6
Hardware: Macintosh Mac OS
: Low normal
Target Milestone: ---
Assignee: Lluis Sanchez
URL:
Depends on:
Blocks:
 
Reported: 2011-09-17 15:00 UTC by dj_technohead
Modified: 2015-07-02 09:07 UTC (History)
3 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED NOT_ON_ROADMAP

Description dj_technohead 2011-09-17 15:00:28 UTC

    
Comment 1 dj_technohead 2011-09-17 15:01:55 UTC
When selecting Version Control\Update on the solution, MonoDevelop appears to update just the main project from SVN but not the other projects in the solution
Comment 2 dj_technohead 2011-09-18 15:54:54 UTC
This is also true for commits.
Comment 3 Lluis Sanchez 2011-09-19 13:54:53 UTC
Are you using the Update command in contextual menu or in the main menu?
Comment 4 dj_technohead 2011-11-15 14:48:51 UTC
I'm using the update command in the contextual menu when right clicking on the solution in the Solution pad.
Comment 5 traderhut 2013-03-30 05:06:16 UTC
I've had the same issue commiting - I have to do 5 commits.. wouldn't be so bad if I could assign a keystroke to it.
Comment 6 Marius Ungureanu 2013-07-22 11:07:59 UTC
traderhut, could you explain how to reproduce this issue?
Comment 7 PJ 2013-11-19 17:04:39 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 8 traderhut 2013-12-04 17:25:14 UTC
Sorry, I didn't reply.

  Due to this bug, I abandoned SVN completely.  (A good idea for everyone on the planet IMHO - out of 9+ version control systems I've used, it is 2nd to the last with only Perforce being worse. - Yes, I'll take Source Safe, or PVCS, or even RCS from 1985 over it.  Although it never happened under Xamarin, I always seem to get working directories hosed up with SVN and they have to be wiped out to make them work again.  And every now and then stuff gets lost when you do that.  - End Soapbox ;-) )

I am now using Git.   As such, I can't reproduce it.

>>> My steps to reproduce it was:   Click on Xamarin Studio.  Open Project.  Not have version control anymore.

Can't get much easier than that. 

For you guys to reproduce it in QA, I would create a project under SVN+SSH on a OLD version of your software, say a year ago, and open it in the current version.  (If that doesn't work, open it in every version between them first.  Or if there is a version you know did something specific with SVN, then maybe try skipping that version or being sure to include it.

I've not tried for the last 4 or so months, so I can't say exactly when it got hosed up.

   -Traderhut
Comment 9 Lluis Sanchez 2013-12-05 05:06:59 UTC
Reopening.