Bug 18271 - I ve got this error when i renaming a class
Summary: I ve got this error when i renaming a class
Status: RESOLVED DUPLICATE of bug 10883
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 4.2.3
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: master
Assignee: Bugzilla
Depends on:
Reported: 2014-03-10 03:14 UTC by Muhammet
Modified: 2014-03-10 14:10 UTC (History)
2 users (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 Muhammet 2014-03-10 03:14:08 UTC
System.IO.IOException: Write fault on path //[Unknown]
  at System.IO.FileStream.WriteInternal (System.Byte[] src, Int32 offset, Int32 count) [0x00097] in /private/tmp/source/bockbuild-mono-3.2.6/profiles/mono-mac-xamarin/build-root/mono-3.2.6/mcs/class/corlib/System.IO/FileStream.cs:651 
  at System.IO.FileStream.Write (System.Byte[] array, Int32 offset, Int32 count) [0x000aa] in /private/tmp/source/bockbuild-mono-3.2.6/profiles/mono-mac-xamarin/build-root/mono-3.2.6/mcs/class/corlib/System.IO/FileStream.cs:627 
  at System.IO.StreamWriter.FlushBytes () [0x00043] in /private/tmp/source/bockbuild-mono-3.2.6/profiles/mono-mac-xamarin/build-root/mono-3.2.6/mcs/class/corlib/System.IO/StreamWriter.cs:222 
  at System.IO.StreamWriter.Decode () [0x0000c] in /private/tmp/source/bockbuild-mono-3.2.6/profiles/mono-mac-xamarin/build-root/mono-3.2.6/mcs/class/corlib/System.IO/StreamWriter.cs:229 
  at System.IO.StreamWriter.FlushCore () [0x00000] in /private/tmp/source/bockbuild-mono-3.2.6/profiles/mono-mac-xamarin/build-root/mono-3.2.6/mcs/class/corlib/System.IO/StreamWriter.cs:201 
  at System.IO.StreamWriter.Flush () [0x00006] in /private/tmp/source/bockbuild-mono-3.2.6/profiles/mono-mac-xamarin/build-root/mono-3.2.6/mcs/class/corlib/System.IO/StreamWriter.cs:195 
  at System.IO.StreamWriter.Dispose (Boolean disposing) [0x00012] in /private/tmp/source/bockbuild-mono-3.2.6/profiles/mono-mac-xamarin/build-root/mono-3.2.6/mcs/class/corlib/System.IO/StreamWriter.cs:178 
  at System.IO.StreamWriter.Close () [0x00000] in /private/tmp/source/bockbuild-mono-3.2.6/profiles/mono-mac-xamarin/build-root/mono-3.2.6/mcs/class/corlib/System.IO/StreamWriter.cs:408 
  at System.Diagnostics.Process.Dispose (Boolean disposing) [0x000a2] in /private/tmp/source/bockbuild-mono-3.2.6/profiles/mono-mac-xamarin/build-root/mono-3.2.6/mcs/class/System/System.Diagnostics/Process.cs:1581 
  at MonoDevelop.Core.Execution.ProcessWrapper.Dispose (Boolean disposing) [0x0007c] in /Users/builder/data/lanes/monodevelop-lion-monodevelop-4.2.3-branch/30c4afc3/source/monodevelop/main/src/core/MonoDevelop.Core/MonoDevelop.Core.Execution/ProcessWrapper.cs:119 
  at System.Diagnostics.Process.Finalize () [0x00000] in /private/tmp/source/boc
Comment 1 Sadik Ali 2014-03-10 04:07:56 UTC
I have check this issue on below environments:

XS 4.2.3 (Build 60)

I tried to reproduce this issue by renaming class name but unable to get any error.
Provide some detail/steps so that I can check this issue.
Comment 2 Muhammet 2014-03-10 04:12:35 UTC
i know. I do not always get this error. I do not see the error will come when. So I do not track:(
Comment 3 Mikayla Hutchinson [MSFT] 2014-03-10 14:10:55 UTC

*** This bug has been marked as a duplicate of bug 10883 ***