Bug 18060 - The remote server returned an error (500) when using linked files set to 'Content' build action
Summary: The remote server returned an error (500) when using linked files set to 'Con...
Status: VERIFIED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 1.10.x
Hardware: PC Mac OS
: High critical
Target Milestone: 1.12 (Merge)
Assignee: Dominique Louis
URL:
: 18038 ()
Depends on:
Blocks:
 
Reported: 2014-02-27 16:46 UTC by PJ
Modified: 2014-03-24 08:46 UTC (History)
8 users (show)

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


Attachments
Sample demonstrating the bug (needs the Tamarin.pdf attachment linked) (809.95 KB, application/zip)
2014-02-27 16:46 UTC, PJ
Details
Pdf to be linked into the attached Sample (302.37 KB, application/pdf)
2014-02-27 16:47 UTC, PJ
Details


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 PJ 2014-02-27 16:46:40 UTC
Created attachment 6177 [details]
Sample demonstrating the bug (needs the Tamarin.pdf attachment linked)

Steps to reproduce:

1) Extract the sample from the attached ZoomingPdfViewer_needs_link_to_pdf.zip
2) Open the ZoomingPdfViewer.sln in Visual Studio
3) Put the attached Tamarin.pdf file on your desktop
4) Right click the solution and choose Add->Existing file
5) Navigate to the desktop and select Tamarin.pdf, but don't click 'Add'
6) Use the dropdown menu next to 'Add' and select 'Add as link'.
7) Set the build action of the Tamarin.pdf file to 'Content'.
7) Attempt to start debugging the app.

Expected:

Tamarin.pdf is transferred to the build server.
App builds, deploys, and runs as expected. 


Actual:

"There were deployment errors. Continue?"

And in the Build output:
The remote server returned an error (500) Internal Server Error


Workaround: 

Instead of linking to the pdf file, choose the regular 'Add'.


This bug occurs with the 1.10.39 release of Xamarin.iOS for VS. It will be fixed for Xamarin.iOS for VS 1.12. For now, please use the workaround.
Comment 1 PJ 2014-02-27 16:47:20 UTC
Created attachment 6178 [details]
Pdf to be linked into the attached Sample
Comment 2 Ram Chandra 2014-02-28 08:40:05 UTC
I try to check this issue and follow all the steps as mentioned in above bug description  and I am able to reproduce it.

Refer screencast : http://screencast.com/t/ulh2vIiBvWgW

Environment:

Windows 7
Microsoft Visual Studio 2013
Microsoft Visual Studio 2012
Xamarin.iOS: 1.10.39
Comment 3 PJ 2014-02-28 11:52:16 UTC
*** Bug 18038 has been marked as a duplicate of this bug. ***
Comment 4 Emmanuel Huna 2014-03-03 20:28:59 UTC
Any timeframe on when the build host will stop crashing if you use linked files?  

Even though I use PCLs, I also use linked files sometimes, especially for cross platform shared resources, where I like to avoid multiple copies of the same image or icon.
Comment 5 PJ 2014-03-04 12:17:47 UTC
This will be fixed in XamarinVS 1.12, which just went into QA for another round of testing. I have no estimate for you, unfortunately.
Comment 6 narayanp 2014-03-24 08:46:37 UTC
I have checked this issue with following builds:

VS 2013/2012/2010
Xamarin for VS 1.12.247
X.iOS 7.2.1-63

Now application builds, deployed and launched successfully. I have add as link pdf file and then run it.

Hence closing this issue