Bug 8392 - Some special characters in project path generates problematic include paths and hint paths in project file
Summary: Some special characters in project path generates problematic include paths a...
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Project Model ()
Version: 3.0.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Lluis Sanchez
: 286 ()
Depends on:
Reported: 2012-11-14 03:13 UTC by Lluis Sanchez
Modified: 2017-09-26 12:30 UTC (History)
3 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 Lluis Sanchez 2012-11-14 03:13:39 UTC
Having a project folder path containing some special characters, such as "(" and ")" (probably others too), causes include paths to be rewritten (if originally from a Visual Studio project) with a big depth till the folder that contain the special characters. Example:

-    <Compile Include="Properties\AssemblyInfo.cs" />
+    <Compile Include="..\..\..\..\..\..\Hello

To reproduce, just create a project which parent folder path contains "(" or

When opening the project on another computer the paths do not match anymore
and files cannot be found.
Comment 1 Jeffrey Stedfast 2012-11-16 17:52:00 UTC
*** Bug 286 has been marked as a duplicate of this bug. ***
Comment 2 Marius Ungureanu 2017-09-26 12:30:28 UTC
This bug does not reproduce anymore.