Bug 16401 - Starter Edition fails when installed to alternate drive.
Summary: Starter Edition fails when installed to alternate drive.
Status: RESOLVED INVALID
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 4.10.1
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
Depends on:
Blocks:
 
Reported: 2013-11-22 10:19 UTC by Scott Coleman
Modified: 2013-11-27 11:34 UTC (History)
1 user (show)

Tags:
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:
Status:
RESOLVED INVALID

Description Scott Coleman 2013-11-22 10:19:15 UTC
Windows verion of Xamarin.Android fails when AndroidSDK is installed to drive D, rather than drive C.

During installation, directed AndroidSDK to drive D.  Xamarin.Android appeared to install completely and correctly, however...

Specifically...
"Tasky" app build succeeded, but would not run.  No devices found.  XStudio was looking for devices in "C:\Users\Scott\.android\avd", but the AVD Manager was manipulating files in "D:\Users\Scott\.android\avd" [C: vs D:] -- this was verified by simply copying files from D:\...\avd to C:\...\avd. 

Generally...
The installation was pretty "dirty" -- portions installed on C:, others on D:.  There is no mechanism for user to specify where all the pieces should go.  [My tiny solid-state C drive should be reserved for system-only; I need to direct all other files to D:.]

[Bug submitted per Michael Hutchison's request in this forum thread: http://forums.xamarin.com/discussion/4697/default-application-is-not-launching-in-emulator]
Comment 1 Mikayla Hutchinson [MSFT] 2013-11-22 13:57:43 UTC
How did you redirect your Windows user profile to drive D?
Comment 2 Scott Coleman 2013-11-27 10:04:04 UTC
This is not a bug.  User error.

After investigating and correcting the redirection of my Windows User Profile, a clean installation of XS, using default destinations, works as expected.

[Thanks to Michael Hutchison for his leading question about how my Windows User Profile was being redirected.  What works is a _complete_ move of the profile to drive D, then "mklink /J C:\Users\Scott D:\Users\Scott".]

I'd still _strongly prefer_ to be able to redirect XS components to preferred destinations [your installation now forces me to consider redirecting C:\Program Files (x86)"], but I can no longer, in good conscience, call this this a "bug".
Comment 3 Jonathan Pryor 2013-11-27 11:34:06 UTC
Marking INVALID as per Comment #2.

> I'd still _strongly prefer_ to be able to redirect XS components to preferred
> destinations [your installation now forces me to consider redirecting
> C:\Program Files (x86)"]

The reason for this is because we need to install files into $(MSBuildExtensionsPath) so that e.g. $(MSBuildExtensionsPath)\Xamarin\Android\Xamarin.Android.CSharp.targets can be found by your .csproj files, and $(MSBuildExtensionsPath) is %ProgramFiles(x86)%\MSBuild.

(We could plausibly reduce what's installed into $(MSBuildExtensionsPath) and have some form of registry lookup or something to have files installed "elsewhere", but this would largely complicate matters, and complication breeds bugs, so this is unlikely to happen.)

You could always move $(MSBuildExtensionsPath)\Xamarin "elsewhere" and use `mklink` so that the directory remains correct...