Bug 2460 - Error occurs in publish the solution under the option Version Control.
Summary: Error occurs in publish the solution under the option Version Control.
Status: VERIFIED INVALID
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Version Control ()
Version: Trunk
Hardware: Macintosh Mac OS
: High major
Target Milestone: ---
Assignee: Alan McGovern
URL:
Depends on:
Blocks:
 
Reported: 2011-12-12 09:03 UTC by narayanp
Modified: 2013-06-17 12:26 UTC (History)
5 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:
VERIFIED INVALID

Description narayanp 2011-12-12 09:03:25 UTC
Steps to reproduce:

1. Launch the MonoDevelop.
2. Start a New Solution or Open the Existing Solution.
3. Solution sidebar appears at the left panel.
4. Right Click on Solution/Project name.
5. Click on the option "Version Control"
6. Click on the option "Publish"
7. Publish window opens up. select the http from the protocol field.
8. Provide the URL "google.com" and click on OK button.
9. Confirmation window opens up, click on OK button.
10. Error pop-up appears.

Actual result:
Error appears in publish the solution.
Details:
System.InvalidOperationException: Operation is not valid due to the current state of the object
  at System.Linq.Enumerable.Single[VersionInfo] (IEnumerable`1 source, System.Func`2 predicate, Fallback fallback) [0x00000] in <filename unknown>:0 
  at System.Linq.Enumerable.Single[VersionInfo] (IEnumerable`1 source) [0x00000] in <filename unknown>:0 
  at MonoDevelop.VersionControl.Repository.GetVersionInfo (FilePath localPath, Boolean getRemoteStatus) [0x00000] in /private/tmp/source/monodevelop/main/src/addins/VersionControl/MonoDevelop.VersionControl/MonoDevelop.VersionControl/Repository.cs:154 
  at MonoDevelop.VersionControl.ChangeSet.AddFile (FilePath file) [0x00000] in /private/tmp/source/monodevelop/main/src/addins/VersionControl/MonoDevelop.VersionControl/MonoDevelop.VersionControl/ChangeSet.cs:98 
  at MonoDevelop.VersionControl.Git.GitRepository.Publish (System.String serverPath, FilePath localPath, MonoDevelop.Core.FilePath[] files, System.String message, IProgressMonitor monitor) [0x00063] in /private/tmp/source/monodevelop/main/src/addins/VersionControl/MonoDevelop.VersionControl.Git/MonoDevelop.VersionControl.Git/GitRepository.cs:339 
  at MonoDevelop.VersionControl.PublishWorker.Run () [0x00000] in /private/tmp/source/monodevelop/main/src/addins/VersionControl/MonoDevelop.VersionControl/MonoDevelop.VersionControl/PublishCommand.cs:95 
  at MonoDevelop.VersionControl.Task.BackgroundWorker (System.Object state) [0x00000] in /private/tmp/source/monodevelop/main/src/addins/VersionControl/MonoDevelop.VersionControl/MonoDevelop.VersionControl/Task.cs:49 

Expected Result:
Error should not occur and solution should be published.

Environment:
MonoTouch 5.0.4
MonoDevelop 2.8.5
mono4Android 4.01
Comment 1 Atin 2011-12-13 06:38:21 UTC
Same error is occurring on windows:

Environments:
Windows7
Mono Develop 2.8.5
Mono for Android 4.0.1
Comment 2 Alan McGovern 2012-01-11 11:52:14 UTC
You cannot use any arbitrary URL as the repository URL so this test will never succeed.
Comment 3 Mohit Kheterpal 2013-06-17 12:26:15 UTC
As pr comment 2, this bug is invalid hence changing its status to verified.