Bug 36632 - can't compile from VS2015 due to newly introduced compile over network check
Summary: can't compile from VS2015 due to newly introduced compile over network check
Status: RESOLVED DUPLICATE of bug 37708
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: General ()
Version: 4.0.0 (C6)
Hardware: Macintosh Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-12-04 20:28 UTC by Bob Japundza
Modified: 2016-01-15 03:47 UTC (History)
5 users (show)

Tags: papercut
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:
RESOLVED DUPLICATE of bug 37708

Description Bob Japundza 2015-12-04 20:28:23 UTC
Getting an exception when compiling a XF project from VS2015 running on Parallels.  The project files are located in the the Mac Documents directory.

From the release notes:

Added an explicit error message “Building from a network share path is not supported at the moment” when attempting to build from an unmapped network share folder on Windows (any path beginning with \\). This is a change to help clarify certain causes of “The “UnpackLibraryResources” task failed unexpectedly”. In its current form, this change will block any attempt to build on a network share that has not been mapped to a drive letter or local folder. This strict rule might be loosened again in the future.

This was not well thought out.  VS2015 does not allow opening projects via the IDE that are on a mapped drive.  I keep the project in the documents directory so I am able to easily use either Xamarin Studio or VS2015.  I don't know of a workaround to this other than to use Xamarin Studio for the time being.
Comment 1 Brendan Zagaeski (Xamarin Team, assistant) 2016-01-15 00:05:10 UTC
Thanks for the report. I have now created an additional bug for this issue to fill in a few details and to ensure optimal tracking. I have mentioned the complication with VS2015 on that report.

*** This bug has been marked as a duplicate of bug 37708 ***
Comment 2 Brendan Zagaeski (Xamarin Team, assistant) 2016-01-15 03:47:51 UTC
> VS2015 does not allow opening projects via the IDE that are on a mapped drive

I have so far not been able to hit that restriction in my test environment [1]. I was able to load an iOS app project that was stored in my Documents folder on my Mac build host mapped to a network share drive letter on Windows.

I tried double-clicking the solution file in Explorer to open it as well as opening the solution via the "File -> Open" menu item in VS. Both were successful.


[1] Test environment 

VS 2015 Update 1

Tested on both:
- Windows 10 on a physical machine
- Windows 8.1 in VMWare Fusion on the Mac build host



## Possible additional information to add

Although I have marked this issue as a duplicate and it might be solved via Bug 37708 fairly soon, in the mean time it wouldn't be a bad idea to:

(a) Attach onto this original bug (Bug 36632) a screenshot or text transcription (or both) of the error that VS 2015 is showing when you attempt to load the solution on the mapped network drive.

(b) Confirm that the same error happens for a new "Visual C# -> iOS -> iPhone -> Single View App (iPhone)" solution that you have just copied into the mapped network drive.