Yes, thank you! I didn't know that existed.
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Suggestion-tp5711662p5711664.html
Sent from the Mono for Android mailing list archive at Nabble.com.
___
Monodroid mailing list
Just a suggestion...
Xamarin should create a webpage where Mono for Android developers can post
links to the apps that they create. This would provide nice examples of what
can be accomplished with your products.
Matt
--
View this message in context:
http://mono-for-android.1047100.n5
.
- Matt
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Mono-for-Android-and-NAnt-tp5710581p5710607.html
Sent from the Mono for Android mailing list archive at Nabble.com.
___
Monodroid mailing list
Monodroid@lists.ximian.com
n
the Android sdk
2) My release target just copies the apk to another directory.
- Matt
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Mono-for-Android-and-NAnt-tp5710581p5710583.html
Sent from the Mono for Android mailing list archive at Nabbl
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/
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/
possible
to add a new target that packages and signs the application, but doesn't
rebuild the main assembly? For example, something like this would work:
Or is there another way to do this that I am missing?
Thanks,
Matt
--
View this message in context:
http://mono-for-android.1047100.n5.nabbl
I have noticed the same behavior. It started happening in version 4.1.
Matt
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Shortcut-disappears-on-every-deploy-tp5709788p5709789.html
Sent from the Mono for Android mailing list archive at Nabble.com
Cool. Thanks for making this available.
Matt
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Android-Play-ExpansionLibrary-C-APK-Expansion-Files-and-LVL-tp5698970p5702032.html
Sent from the Mono for Android mailing list archive at Nabble.com
Nevermind. This was also caused by a bad install on my other machine. I did a
repair install and it appears to be working now.
Matt
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/MonoAndroidBinPath-error-with-4-2-tp5699377p5701987.html
Sent from the Mono for
es" task. Verify the parameter exists on the task, and it is
> a
> settable public instance property.
>
I am getting this error when trying to build my project in Release mode. I
tried linking "Sdk Assemblies Only" and "Sdk and User Assemblies" and
neither one
-installed
fixed it.
Matt
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/MonoAndroidBinPath-error-with-4-2-tp5699377p5700085.html
Sent from the Mono for Android mailing list archive at Nabble.com.
___
Monodroid ma
until monodroid version 4.1. I
verified that your solution builds fine, but it appears to require including
all projects in the same solution. I suppose I can do it this way, but I am
confused as to why this is required and why the requirement changed in
monodroid 4.1. Does this make sense?
Thanks,
Mat
clue as to what the underlying problem is.
Matt
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/New-Binding-Generator-tp5623432p5673440.html
Sent from the Mono for Android mailing list archive at Nabble.com.
___
Monodroid
this post. AndroidClassLibrary1.dll is included in AndroidApplication1, and
AndroidApplication1 fails to build with the error above.
Matt
http://mono-for-android.1047100.n5.nabble.com/file/n5672918/BuildProblem.zip
BuildProblem.zip
--
View this message in context:
http:/
mine, but I
don't know what that is. Since I opened your project, I am using the same
exact jar file that you used. See the attached image.
http://mono-for-android.1047100.n5.nabble.com/file/n5672627/lvl2screenshot.png
Matt
--
View this message in context:
http://mono-for-android.10471
Atsushi,
It looks like you made some changes to your lvl and rebuilt today, since the
modified date is 2pm today. I agree that what you have now contains all the
types where the one you posted yesterday did not. What did you change to
make the binding generator generate all of the types?
Matt
o the obfuscation step is
overwritten.
Matt
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Linking-problem-with-obfuscated-assembly-tp5666519p5670786.html
Sent from the Mono for Android mailing list archive at Nabbl
d assembly.
Thanks,
Matt
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Linking-problem-with-obfuscated-assembly-tp5666519p5670720.html
Sent from the Mono for Android mailing list archive at Nabble.com.
___
Monodroid ma
it in Reflector. For
example, the LicenseChecker class does not exist in the output assembly.
Matt
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/New-Binding-Generator-tp5623432p5670080.html
Sent from the Mono for Android mailing list archive at Nabbl
ResponseData
ServerManagedPolicy
StrictPolicy
ValidationException
Is this the expected behavior and the missing types have to be added
manually, or is the generator still not working correctly?
Thanks,
Matt
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/New-Binding
this problem before 4.1.0. Has anyone found a fix for this problem?
Thanks,
Matt
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/msbuild-crash-in-ResolveLibraryProjectImports-task-in-MFA-v4-1-tp5635151p5668932.html
Sent from the Mono for Android mail
the linking process succeeds,
but I have another problem. The SignAndroidPackage target appears to rebuild
the assembly for my main application, because the assembly that gets added
to the apk is not obfuscated. Am I calling the correct build targets in the
correct order?
Thanks,
Matt
--
View t
Is anyone else responding to accelerometer
events in a similar way? By the way, this occurs on a real hardware device -
LG Optimus V.
Thanks,
Matt
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/ANR-using-Sensor-Manager-tp5637205p5637205.html
Sent from the Mono f
A week sounds much better. :)
Thanks,
Matt
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/New-Binding-Generator-tp5623432p561.html
Sent from the Mono for Android mailing list archive at Nabble.com.
___
Monodroid
A month is actually a long time :(. Is there a set date for the final
release?
Thanks,
Matt
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/New-Binding-Generator-tp5623432p5631555.html
Sent from the Mono for Android mailing list archive at Nabble.com
I didn't realize the fix you mentioned was in the binding generator. Will
this be in the next alpha release?
Thanks,
Matt
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/New-Binding-Generator-tp5623432p5630407.html
Sent from the Mono for Android mailing
ounds like you are seeing difference results. Can you post your project
so that I can see what I am doing wrong?
Thanks for your help.
Matt
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/New-Binding-Generator-tp5623432p5627655.html
Sent from the Mono for Android ma
nsing working.
Matt
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/New-Binding-Generator-tp5623432p5624086.html
Sent from the Mono for Android mailing list archive at Nabble.com.
___
Monodroid mailing list
Monodroid@lists.ximia
29 matches
Mail list logo
