Bug 6334 - Version Control Errors commiting SVN
Summary: Version Control Errors commiting SVN
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Version Control ()
Version: 3.0.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Alan McGovern
Depends on:
Reported: 2012-07-31 05:16 UTC by pedrohex
Modified: 2012-11-21 07:22 UTC (History)
1 user (show)

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:

Description pedrohex 2012-07-31 05:16:28 UTC
SVN version control is not working well since version .
I've installed v3.0.3.4 and many error occur. Some times whole solution get's breaked .
Stetic generator keeps giving me too much errors in this version . Duplicate variables names, code generation error ... i dont know what major changes have been made from but this version's 3 are a lot worst , in my particular case. Can you please verify if somethig misses from back versions ? expecially with version control ?

Thanks in advance.
Comment 1 Alan McGovern 2012-11-21 07:22:33 UTC
I have not been able to reproduce these errors and there have been some fixes in this area since If they still persist in more recent versions of MonoDevelop could you reopen this bug and provide information on how to reproduce the bug. Thanks!