Geek Answers Handbook

Proguard greyed in specific build configurations

I created two build configurations (settings copied from Release) to separate the free / premium feature installed in my application using compiler constants. If you select any of these new configurations, the Enable Proguard checkbox turns gray / disabled. It is only available when you select the initial release build configuration.

I searched everywhere what I know about differences in build configurations, but can't find them. What am I missing, what needs to be changed so that Enable Proguard is not limited to only one initial release build configuration?

Update. I tried to compare the assembly configurations in my .csproj file, and this did not show a reason. Even copying complete and accurate settings from the "Release" configuration to the "Release-Free" and "Release-Premium" configurations does not allow ProGuard to be included in VS. Adding a line <EnableProguard>True</EnableProguard>to the configuration also does not affect VS in any way.

+4
source share
1 answer

Conducting a comment on the question as an answer. Glad he was able to help you, but he definitely still sounds like a bug that might be good to report.

<EnableProguard>True</EnableProguard> , , , , Proguard APK.

+1

More articles:


All Articles