Bug 24868 - Cannot build when user home folder has non-english chars in name
Summary: Cannot build when user home folder has non-english chars in name
Status: VERIFIED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: General ()
Version: 4.0.0 (C6)
Hardware: PC Windows
: Normal normal
Target Milestone: 15.4
Assignee: Bugzilla
URL:
: 39962 ()
Depends on:
Blocks:
 
Reported: 2014-11-26 15:14 UTC by J.C.Ködel
Modified: 2017-07-28 10:13 UTC (History)
8 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 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 FIXED

Description J.C.Ködel 2014-11-26 15:14:39 UTC
My Windows user name is JúlioCésar, hence, my home folder is located at c:\users\júliocésar, but Xamarin doesn't seems to understand non-english chars in file names:

Show Details	Severity	Code	Description	Project	File	Line
	Error		Unexpected error - Please file a bug report at http://bugzilla.xamarin.com. Reason: System.UnauthorizedAccessException: Access to the path "c:\users\j├║lioc├®sar" is denied.	App1.Droid		



Instead of ú, it tries to find ├║
Instead of é, it tries to find ├®
Comment 1 asimk 2014-12-08 08:06:37 UTC
I have checked it at my end and I am also observing same Issue.

Checked with builds:
VS 2013
XVS 3.8.150

http://www.screencast.com/t/wUhWyYt7ER
Build Output: https://gist.github.com/saurabh360/5992d8ee67ee7fa3d6e7
VS Trace log: https://gist.github.com/saurabh360/99e8dd4d0548177e5442
Comment 2 Jon Goldberger [MSFT] 2015-03-06 14:07:24 UTC
Possibly related bug: #27735
Comment 3 Matt Ward 2016-07-08 10:41:20 UTC
*** Bug 39962 has been marked as a duplicate of this bug. ***
Comment 4 Juan Marcelo Tondato 2017-06-27 12:49:17 UTC
Hi,
I can not reproduce the bug with 15.4 version.

I'm resolving it tentatively as Fixed.

That said, if you're still facing this issue with current bits, please feel
free to reopen the bug.
Thanks