Using the AfterBuild target appears to work correctly. Now, the linking step
is failing due to the obfuscated assembly, but that's a different problem
that I need to investigate. Thanks for all the help.
Matt
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Build-Ta
On 5/22/2012 11:05 AM, Matt wrote:
Thanks for the quick response. Signing the package is straightforward, but
what about creating the apk? Is there an existing build target that creates
the apk but doesn't rebuild the main assembly?
No, there is not, as the apk requires the main assembly.
You
On May 22, 2012, at 12:05 PM, Matt wrote:
> Thanks for the quick response. Signing the package is straightforward, but
> what about creating the apk? Is there an existing build target that creates
> the apk but doesn't rebuild the main assembly?
What you could instead do is build the obfuscated as
Thanks for the quick response. Signing the package is straightforward, but
what about creating the apk? Is there an existing build target that creates
the apk but doesn't rebuild the main assembly?
Thanks,
Matt
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Build-
You can sign the package manually:
http://docs.xamarin.com/android/tutorials/Preparing_Package_for_Android_Marketplace
Or you can create your own MSBuild target.
Jonathan
On 5/21/2012 10:08 PM, Matt wrote:
The *SignAndroidPackage* depends on the build target, so it always rebuilds
the applic
The *SignAndroidPackage* depends on the build target, so it always rebuilds
the application before packaging and signing. This makes it impossible (that
I know of) to obfuscate the main application assembly and rely on the
SignAndroidPackage target to package the obfuscated assembly. Is it possible
