Bug 6735 - MonoDevelop writes/used to save utf-16 .csproj files in utf-8 encoding and without BOM
Summary: MonoDevelop writes/used to save utf-16 .csproj files in utf-8 encoding and wi...
Status: NEW
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Project Model ()
Version: Trunk
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Lluis Sanchez
Depends on:
Reported: 2012-08-29 10:06 UTC by Marek Habersack
Modified: 2012-08-29 10:06 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 for Bug 6735 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Marek Habersack 2012-08-29 10:06:32 UTC
Such files break Visual Studio since it sees the utf-16 encoding in the XML header but since the file has no BOM it cannot make sure that it indeed is encoded in utf-16. There are two MonoTouch samples which have .csproj files like that: