Bug 17434 - ContentCopier cannot find linked files when doing remote build
Summary: ContentCopier cannot find linked files when doing remote build
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 1.10.x
Hardware: PC Windows
: --- normal
Target Milestone: 1.12 (Merge)
Assignee: Marek Habersack
Depends on:
Reported: 2014-01-26 03:17 UTC by apollo_maverick
Modified: 2014-01-30 10:24 UTC (History)
4 users (show)

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

test (104.34 KB, application/octet-stream)
2014-01-29 07:17 UTC, apollo_maverick

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:

Description apollo_maverick 2014-01-26 03:17:42 UTC
looks like that caused by all files added to VS using "Add as link" do not get copied to OSX mtbs project build source path.

Xamarin.iOS for VS 1.10.39

log on OSX:
Running tool: ContentCopier
[26-Jan-2014 15:54:45] Error: Tool MonoTouch.Tools.Tools.ContentCopier failed to run
[26-Jan-2014 15:54:45] Exception: Exception type: System.InvalidOperationException
Source file '/Users/xxx/Library/Caches/Xamarin/mtbs/builds/test/c4afe79d-e2a4-4baa-bcde-428b54956352/Assets/images/a.xnb' does not exist
  at MonoTouch.Tools.Tools.ContentCopier.RunInner (MonoTouch.Tools.Tools.RunInfo ri) [0x00000] in <filename unknown>:0 
  at MonoTouch.Tools.Tools.ToolBase.Run () [0x00000] in <filename unknown>:0 
  at Mtb.Server.Commands.Build.RunTools (System.Collections.Generic.List`1 tools, ILoggingHelper logger) [0x00000] in <filename unknown>:0
Comment 1 Marek Habersack 2014-01-27 08:03:26 UTC

I haven't been able to reproduce the problem with the specified versions as described. Could you please attach the project which fails to build for you?
Comment 2 apollo_maverick 2014-01-29 06:37:03 UTC
How couldn't you be able to reproduce?

1 create an basic iOS app using the template in VS2013

 add an existing pic to Resources using "Add As Link" (right click on Resources folder in the Solution Explorer -> Add... -> Add Existing Item... -> choose a picture -> click the DOWN arrow on the add button to choose "Add As Link"

3 run/debug with simulator or devices from VS2013

you'll see the error
Comment 3 Marek Habersack 2014-01-29 06:57:23 UTC
That's exactly what I did and I got no error - hence my request for the repro.
Comment 4 apollo_maverick 2014-01-29 07:17:11 UTC
Created attachment 5930 [details]

VS2013 debug out:

2>Server command 'Build': application remote build failed
2>Command execution task ended with exception
2>Exception System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
2>Exception details can be found in the log file
2>Remote build step failed.
2>Done building target "_BuildNativeApplication" in project "Empty1.csproj" -- FAILED.
2>Done building project "Empty1.csproj" -- FAILED.
2>Build FAILED.
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
Comment 5 Marek Habersack 2014-01-29 12:12:43 UTC

Thanks for the repro - I was able to reproduce the problem with your test project. The problem is fixed in our repositories but, unfortunately, it is too late for the fix to make it to the 1.10 release :( The fix will be part of the next, 1.12, release.

In the meantime you will unfortunately need to copy the file instead of linking to it.
Comment 7 apollo_maverick 2014-01-29 13:32:27 UTC
when will 1.12 be released? thanks
Comment 8 Marek Habersack 2014-01-29 15:14:42 UTC
It is due to enter QA testing soon, but I cannot give you any exact date, I'm sorry. Keep your eye on Alpha and Beta channel updates, however, it will hit them as soon as it's OK-ed by QA.
Comment 9 Mohit Kheterpal 2014-01-30 10:24:32 UTC
Today we have checked this issue with following builds :

VS 2013
Xamarin for VS (3f8cecdd5d00f0366e31218f111ce20c1c216cd0)
Xamarin.iOS (Business Edition)Hash: 8400ec3

We are able to build and deploy application on device and simulator given in comment 4.

Hence closing this issue.