(Sorry for the late reply, I've been away during the holiday week.)
Whoa, that is weird and yes that does not make sense. But still good to
know that now you got your stuff working :)
I'll investigate this issue as requiring VS11 beta is almost no-go - I'm
not sure how long it would need to i
Thanks Matt (and Nick)
Installing Visual Studio 11 Beta worked! :-)
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/New-Binding-Generator-tp5623432p5673598.html
Sent from the Mono for Android mailing list archive at Nabble.com.
Just as Nick mentioned, I installed Visual Studio 11 Beta, and now the
Binding Generator emits all of the types. :) Please note that I am still
using Visual Studio 2010. The only thing that I did was install VS11 Beta.
This makes absolutely no sense to me, but will hopefully give the M4A guys a
clu
I'm using Visual Studio 2010 Professional service pack 1 (sorry should have
mentioned that in my previous post) and is all up to date.
Doesn't the binding generator work for this version?
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/New-Binding-Generator-tp5623
Atsushi,
I am completely stumped. I downloaded your project, and before building it,
I opened the output in Reflector and saw all the types. I then opened the
project in Visual Studio and rebuilt, and now the additional types are
missing. Something is different with your build environment than min
update your developer enviroment!
like download the vs2011 and install. and you will dont get this issue
anytime.
i think resolve the problem if you update .net framework 4.0 from
microsoft.com.
Nick
On Apr 28, 2012 1:11 PM, "Mark Eaton" wrote:
> Hi, I'm still getting this issue with Google An
Hi, I'm still getting this issue with Google Analytics after the new Alpha
download: 4.1.1.
I'm using the JAR from this link:
https://developers.google.com/analytics/devguides/collection/android/
Is there something I'm doing wrong here?
The error is:
BINDINGSGENERATOR : warning : failed to pars
Yes, but I didn't modify it. Instead I created a new project.
The new project ("lvl2") is bound to the jar that I build from the
*latest* google extras package, just to make sure it binds the latest
library without problem.
Yet, the old library (the one in "lvl.zip") should have bound fine, as
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
--
Hello,
On 2012/04/27 22:30, Nick wrote:
Hy!
I have same issue:
What are you trying to do? It does *not* look like the same issue anyways.
Warning 1 failed to parse assembly C:\Program Files (x86)\Reference
Assemblies\Microsoft\Framework\MonoAndroid\v1.0\mscorlib.dll:
System.TypeInit
Did you really see my archive? It contains the *working* build as an
evidence that it certainly works.
This is the screenshot of Reflector that loads my dll. I hope this is
understood obviously.
http://dl.dropbox.com/u/493047/2012/04/lvl-certainly-bound.png
Atsushi Eno
On 2012/04/27 21:03, M
I found the solution!
I have installed the VS11 Beta and the builded bindig project successful!
Maybe the .NET 4.5 is the difference?
2012/4/27 Nick :
> Hy!
>
>
> I have same issue:
> Warning 1 failed to parse assembly C:\Program Files (x86)\Reference
> Assemblies\Microsoft\Framework\MonoA
Hy!
I have same issue:
Warning 1 failed to parse assembly C:\Program Files (x86)\Reference
Assemblies\Microsoft\Framework\MonoAndroid\v1.0\mscorlib.dll:
System.TypeInitializationException: The type initializer for
'Mono.Cecil.Metadata.TableHeap' threw an exception. --->
System.ArgumentExcep
Hi Atsushi,
Thanks for the quick reply. The problem isn't building the project, I can do
that just fine. The problem is that the library that is produced does not
contain all of the classes that are in the jar file. I verified this is a
problem with the library you built as well by opening it in R
I just verified that the latest lvl binds successfully on Windows. Here
is the proof:
http://dl.dropbox.com/u/493047/2012/04/lvl2.zip
Only one Metadata.xml fixup was required to build it.
I repeat some important notes.
How did you build LVL jar? Note that there is *no* built-in jar for that
l
The binding generator still does not appear to be working correctly in 4.1.1,
at least how I would expect it to work. Here are the list of types that it
generates:
IDeviceLimiter
IDeviceLimiterInvoker
ILicenseCheckerCallback
ILicenseCheckerCallbackInvoker
IObfuscator
IObfuscatorInvoker
LicenseChec
Hi
Just wondering if there are any updates on this. My alpha version is still
4.1.
I'm getting the same issue when using the libGoogleAnalytics.jar
Regards
Mark Eaton
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/New-Binding-Generator-tp5623432p5663779.html
S
I never misspoke, but instead of pointless argument I'll stop giving
extraneous comments on my replies here. Thanks.
Atsushi Eno
Jonathan Pryor wrote:
On Apr 10, 2012, at 9:24 PM, Matt wrote:
A month is actually a long time :(. Is there a set date for the final release?
Eno mis-spoke. We're
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 mail
On Apr 10, 2012, at 9:24 PM, Matt wrote:
> A month is actually a long time :(. Is there a set date for the final release?
Eno mis-spoke. We're planning on the next preview release in about a week.
- Jon
___
Monodroid mailing list
Monodroid@lists.ximia
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.
_
Yes it will. It shouldn't take long (like a month) until the next
preview release.
Atsushi Eno
Matt wrote:
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.10471
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 list archiv
I'm having that same problem. It builds, no errors, but I get the above
errors in the Build Output window. Then the dll generated from the build
has nothing relevant in it.
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/New-Binding-Generator-tp5623432p5627672.htm
I didn't have any errors building the project - only warnings similar to the
original post in this thread. My build produced a dll and when I looked at
it in the reflector, I could see that only a few interfaces were imported by
the binding generator and most of the types were missing.
It sounds l
Hello,
On 2012/04/07 13:01, Matt wrote:
I am seeing the same problem. I am trying to bind the licensing libraries
from google. In addition to the warnings, I noticed that most of the types
are not imported by the binding generator. I'm not sure if this is related
to the warnings, but it is a sho
I am seeing the same problem. I am trying to bind the licensing libraries
from google. In addition to the warnings, I noticed that most of the types
are not imported by the binding generator. I'm not sure if this is related
to the warnings, but it is a show stopper for getting the licensing working
27 matches
Mail list logo
