Bug 13117 - XS completely messes up project ItemGroup relative paths
Summary: XS completely messes up project ItemGroup relative paths
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 4.0.9
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: master
Assignee: Bugzilla
Depends on:
Reported: 2013-07-09 07:41 UTC by Goncalo Oliveira
Modified: 2013-07-15 20:38 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Visual Studio solution (147.22 KB, application/x-zip-compressed)
2013-07-10 04:43 UTC, Goncalo Oliveira
Xamarin Studio solution (29.94 KB, application/x-zip-compressed)
2013-07-10 04:49 UTC, Goncalo Oliveira
Messed up project (5.02 KB, text/plain)
2013-07-15 07:09 UTC, Goncalo Oliveira

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 Goncalo Oliveira 2013-07-09 07:41:52 UTC
This is a really annoying bug for anyone using VS and XS. Which is everyone who wants to use VS, only that it's not possible to just use VS, whether it's the existing bugs or the need to build XIB interfaces.

Xamarin Studio completely messes the relative paths in the project file. They go perfectly clean from Visual Studio, with paths relative to project file, but when XS picks them up, it insists on using the relative path from root! wtf?? So what is a beautiful relative path, like 'Model\MyModelFile1' becomes a piece of trash like '..\..\..\trunk\solutionfolder\projectfolder\Model\MyModelFile1'.

Xamarin Studio 4.0.9 (build 12)
Comment 1 Mikayla Hutchinson [MSFT] 2013-07-09 15:47:34 UTC
Do you have a repro for this? I'm not seeing it with our projects.
Comment 2 Goncalo Oliveira 2013-07-10 04:43:48 UTC
Created attachment 4301 [details]
Visual Studio solution

This is the Visual studio project, before sending over to the other side. Has nothing special really, just the Hello World project and a linked file (which does not seem to have anything to do with it).
Comment 3 Goncalo Oliveira 2013-07-10 04:49:57 UTC
Created attachment 4302 [details]
Xamarin Studio solution

This is the Xamarin Studio solution with the messed up project! I had to make two tries, my first attempt didn't quite work. It seems that special characters have some saying in this.

Attempt 1
Full path to project was

Attempt 2
Full path to project was
/Users/username/Documents/crazy drunk (duffbeer)/HelloWorld_App2/HelloWorld_App2

Did not try without the '()' characters to know if spaces are enough, but one of those is screwing things up. My SVN path is configured like that 'svnname (trunk)' so this was happening from the start.
Comment 4 Goncalo Oliveira 2013-07-10 04:50:39 UTC
Above attachments and comments should be more than enough.
Comment 5 Mikayla Hutchinson [MSFT] 2013-07-12 16:54:38 UTC
Works fine for me with master. Can you reproduce it with the current Xamarin Studio alpha?
Comment 6 Mikayla Hutchinson [MSFT] 2013-07-14 14:54:52 UTC
Although you reported this on Windows, i assume it's Mac, since the project is an iOS project and won't open in XS on Windows.
Comment 7 Goncalo Oliveira 2013-07-15 05:34:35 UTC
@Michael Hutchinson you're correct, it's with Mac version - because I started talking about the visual studio solution my brain automatically chose Windows but the issue is with XS for Mac, not VS.

I don't usually use alpha releases for production. Most I can do is install to try it out.
Comment 8 Goncalo Oliveira 2013-07-15 07:06:40 UTC
Changed to alpha channel. Still happens...

=== Xamarin Studio ===

Version 4.1.6 (build 2)
Installation UUID: 7af9a0e0-546a-4461-b9ca-1a6a341c892e
	Mono 3.0.12 ((no/d6c5db8)
	GTK 2.24.18
	GTK# (
	Package version: 300120000

=== Xamarin.Android ===

Not Installed

=== Apple Developer Tools ===

Xcode 4.6.1 (2067)
Build 4H512

=== Xamarin.iOS ===

Version: (Business Edition)
Hash: b7e6b95
Build date: 2013-03-07 10:27:05-0400

=== Xamarin.Mac ===

Xamarin.Mac: Not Installed

=== Build Information ===

Release ID: 401060002
Git revision: dc82b708c19d7fa1dc3ad314cc6daf2151813130
Build date: 2013-07-11 20:50:47+0000
Xamarin addins: 97527c853b2a4f05cc024e3109368091be7f9d4f

=== Operating System ===

Mac OS X 10.8.4
Darwin goliveiramac.local 12.4.0 Darwin Kernel Version 12.4.0
    Wed May  1 17:57:12 PDT 2013
    root:xnu-2050.24.15~1/RELEASE_X86_64 x86_64
Comment 9 Goncalo Oliveira 2013-07-15 07:09:31 UTC
Created attachment 4343 [details]
Messed up project

path to project file

/users/username/Documents/crazy drunk (duffbeer)/HelloWorld_App2/HelloWorld_App2

Again, the ' (duffbeer)' seems to be the responsible.
Comment 10 Goncalo Oliveira 2013-07-15 07:17:22 UTC
Seems to be related:
Comment 11 Goncalo Oliveira 2013-07-15 07:19:16 UTC
May also related:
Comment 12 Mikayla Hutchinson [MSFT] 2013-07-15 20:38:01 UTC
Okay, so it only happened if there were characters in the project's path. The problem was that XS escaped the path, then tried to make it relative to the *unescaped* project directory.