Bug 54642 - ProGuard installation is unusable
Summary: ProGuard installation is unusable
Status: RESOLVED DUPLICATE of bug 32861
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 7.2 (15.1)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: dean.ellis
Depends on:
Reported: 2017-04-06 14:32 UTC by Michael Rumpler
Modified: 2017-06-13 18:30 UTC (History)
7 users (show)

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:

Description Michael Rumpler 2017-04-06 14:32:09 UTC
I just installed a new machine with VS2017 and I got the same problems I had years ago when I first needed to get ProGuard running on my old machine with VS2015. So I thought I'll open a bug because it seems nobody at Xamarin ever uses ProGuard at all or you would've recognized this yourself.

1) ProGuard is installed to C:\Program Files (x86)\Android\android-sdk\tools\proguard

But unfortunately ProGuard fails to run when it is installed in a folder which contains a space. So "Program Files (x86)" does not work. Visual Studio or MSBuild both raise "C:\Program Files(Access Denied)" errors.

There are several threads in the forum which describe how to handle this. I followed https://forums.xamarin.com/discussion/comment/147029/#Comment_147029 and created a symbolic link to the android-sdk with

mklink /j C:\android-sdk "C:\Program Files (x86)\Android\android-sdk"

Then I needed to change the path to the SDK in Visual Studio / Options / Xamarin.
But you could also install the Android SDK in a different folder from the start.

2) an old version of ProGuard is installed

The installed version doesn't run with Android 7 anymore. I think 6 failed already. So I needed to download the most recent version from https://sourceforge.net/projects/proguard/files/ and use that instead. But beware that you copy the proguard*.txt files to the new folder or the next error will bite you. That information came from Xamarins own Jon Douglas http://stackoverflow.com/a/39514706 btw., so you already know what to do.

Every user who wants to use ProGuard with Xamarin runs into those problems. Why don't you just change your installation to do that by default?

And when you're already into changing the setup procedure, why don't you ask James Montemagno what else has to be done to get Xamarin.Android ready to work AFTER the setup routine. http://motzcod.es/post/158155898027/setting-up-vs-2017-for-xamarin-dev
I would expect that I install VS with Xamarin and I can start coding. That works well with pure VS for Windows, but not with Xamarin.Android.
Comment 1 Peter Collins 2017-06-13 18:30:43 UTC

*** This bug has been marked as a duplicate of bug 32861 ***