Bug 3993 - MonoDevelop gives you version control options and initializes an empty git repository, even when publishing fails.
Summary: MonoDevelop gives you version control options and initializes an empty git re...
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Version Control ()
Version: 2.8.8.1
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Alan McGovern
URL:
: 3996 ()
Depends on:
Blocks:
 
Reported: 2012-03-20 14:42 UTC by Zane
Modified: 2012-07-06 13:36 UTC (History)
2 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 FIXED

Description Zane 2012-03-20 14:42:28 UTC
Prerequisites:
MonoDevelop Installed
You have created a new remote repository somewhere (i.e. GitHub)

Steps to reproduce:
- Open MonoDevelop
- Create a new solution
- Right click on the new solution and click Version Control -> Publish
- You will be prompted with a dialog.Purposefully enter some of the information in wrong. Either By using SVN instead of git or putting the wrong URL in, in order for the publish operation to fail.
- Observe that a new empty repository is created in your project directory
- Observe that version control features are now present under version control, prohibiting you from attempting to republish.

I'm not sure if this is proper functionality or not. I think publish is just a bunch of different version control actions lumped into one feature. So if one of those actions doesn't get done then that might be intended. The only thing is you can't really use publish again once it's been done once.
Comment 1 Mikayla Hutchinson [MSFT] 2012-04-26 21:16:54 UTC
*** Bug 3996 has been marked as a duplicate of this bug. ***
Comment 2 Alan McGovern 2012-07-05 09:07:27 UTC
Fixed in git master. There is still an issue where sometimes the overlay icons are not removed from the solution pad, though I'm not sure why they are being added in the first place. They must be added asynchronously and we lack the facilities to properly remove a project from version control other than by reloading the entire solution.
Comment 3 Chris 2012-07-06 13:29:44 UTC
This does not appear to be fixed.
I am using 3.03.2 (Mac, Lion) and it is still happening.
I am trying to publish to a git repository on a network machine (actually a Windows PC) and do not know how to complete the 'Connect to Repository' dialog. So the repository isn't found but the solution is now 'published' to a nonexistent repository, and nothing further can be done, except 'remove' from version control , which removes all the source files  as well - surely it should not do this; removing from source control should remove only the linking, not the original files!
If it's any help I have years of experience with Microsoft SourceSafe but none (yet) with git.
Comment 4 Chris 2012-07-06 13:32:52 UTC
Sorry, looking at the dates I see this was only fixed yesterday so I won't have the update yet. I wish someone would 'fix' the discrepancy between US and Euro dates, I thought it was fixed on 7th May, not 5th July!
Comment 5 Alan McGovern 2012-07-06 13:36:42 UTC
No problem, i've made that mistake before too.

I did file the issue you mentioned at the end of comment 3 as bug #6014. If the description of the issue is incomplete, could you add additional information to it? This is definitely not something that should happen.