Bug 13840 - Solution changes aren't visible after recent update
Summary: Solution changes aren't visible after recent update
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Version Control ()
Version: 4.0.11
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: master
Assignee: Marius Ungureanu
URL:
Depends on:
Blocks:
 
Reported: 2013-08-07 20:29 UTC by Ievgen
Modified: 2013-09-09 12:49 UTC (History)
1 user (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 FIXED

Description Ievgen 2013-08-07 20:29:17 UTC
After upgrading to a new stable Studio 4.0.11 (build 6), I can't see any solution changes to push it to my Git repo. It just shows that "No files have local modifications", but file icons in Navigator panel show changes.

As a walk-around I have to use XCode Organizer, there I can see all changes.
Comment 1 Marius Ungureanu 2013-08-08 11:19:39 UTC
This has been fixed and will be included in the following releases. ;D
Comment 2 Ievgen 2013-08-09 01:57:46 UTC
When should we wait another "stable" release then? =)
Comment 3 Ievgen 2013-08-09 02:02:35 UTC
I mean, the today's update to 4.0.12 (build 3) doesn't have the fix yet ;-(
Comment 4 Marius Ungureanu 2013-08-09 05:34:13 UTC
I'll ask the team to include the fix.
Comment 5 Ievgen 2013-09-07 16:27:02 UTC
Hey guys, any news on this item? It's been a month already and I've seen several updates but the issue is still valid and there is no way to see the changes made in solution. I think this is a blocker.
Comment 6 Marius Ungureanu 2013-09-07 17:37:08 UTC
The latest alpha should have this fix.
Comment 7 Ievgen 2013-09-07 17:38:33 UTC
Yes, I checked it in Alpha and indeed it has a fix there, but it doesn't seem realistic to work on Alpha for a big project.
Comment 8 Marius Ungureanu 2013-09-08 07:30:29 UTC
A stable release will occur pretty soon. The problem was that the fixes couldn't get cherry-picked into the branch without cherry-picking 20 other commits.