Hi Stephan
On 2012.08.28 12:49, Stephan Steiner wrote:
Hi mel
I think it's the language barrier - I felt you were hinting at "it's not
appropriate to complain" - and I think it's appropriate if you have just
cause.
It seems so. Sorry for misunderstanding.
We have the situation where you can c
yeah I have to say the majority of questions I see come across this list as
"problems" are more related to the android os, not the the m4a. One of the
most common one's I've seen is in regards to listview and getting an item
at a certain position. The docs are obfuscated in a way and that's when yo
Hi mel
I think it's the language barrier - I felt you were hinting at "it's not
appropriate to complain" - and I think it's appropriate if you have just
cause.
We have the situation where you can call some code and don't really know
whether it will work until you've tried (e.g. getting the networ
Thanks Sayed
On 2012.08.20 00:23, Sayed Arian Kooshesh wrote:
You have to understand, android is flawed, too. What you get with this
product is a lot of headache removal from learning java and it's
f*cked up ways.
I'm trying not to blame anyone. Android is there and we have to live
with that.
You have to understand, android is flawed, too. What you get with this
product is a lot of headache removal from learning java and it's f*cked up
ways.
On Sun, Aug 19, 2012 at 5:22 PM, Stephan Steiner
wrote:
> Hi mel
>
> Well.. aren't we all paying customers that Xamarin needs to listen to?
> Sit
yeah i agree
System.AppDomain.CurrentDomain
.UnhandledException +=
worked for me
On Sun, Aug 19, 2012 at 1:48 AM, Miljenko Cvjetko wrote:
> Hi Stephan
>
>
> On 2012.08.19 02:36, Stephan Steiner wrote:
>
>> Mel
>>
>> I think it's a WFC stack issue, too. I'm a bit unhappy though that I get
>> th
seems like you are missing your debug symbols, compile and export with
debug symbols :D
On Thu, Aug 16, 2012 at 3:17 PM, Stephan Steiner
wrote:
> Hi
>
> I guess I'm missing something. I'm developing a mobile version of a client
> that is already available on PCs in multiple forms. Those different
Hi Stephan
On 2012.08.20 00:22, Stephan Steiner wrote:
Hi mel
Well.. aren't we all paying customers that Xamarin needs to listen to?
Sitting on your mouth if you think something is wrong with the product you
purchased seems wrong to me.
What have I done wrong? Sat on my mouth if I thought some
Hi mel
Well.. aren't we all paying customers that Xamarin needs to listen to?
Sitting on your mouth if you think something is wrong with the product you
purchased seems wrong to me.
Your tips about additional exception handlers helped somewhat... now I can
catch them and the final straw seems to
Hi Stephan
On 2012.08.19 02:36, Stephan Steiner wrote:
Mel
I think it's a WFC stack issue, too. I'm a bit unhappy though that I get
those uncaught exceptions.. that's a "musn't happen" case for me. Throw me
any exception back to my code is fine, but just crashing the app isn't.
I can understand
Mel
I think it's a WFC stack issue, too. I'm a bit unhappy though that I get
those uncaught exceptions.. that's a "musn't happen" case for me. Throw me
any exception back to my code is fine, but just crashing the app isn't.
After a lot of trial and error I managed to get a combination of
ServiceS
Hi Stephan
On 2012.08.18 21:18, Stephan Steiner wrote:
mel, craig
I've gone ahead and recreated all my libs using the shared file approach,
than made sure I compile my MA project with those. Now I can step into the
lib, but something is still very wrong - the debugger ends on the wrong line
(st
mel, craig
I've gone ahead and recreated all my libs using the shared file approach,
than made sure I compile my MA project with those. Now I can step into the
lib, but something is still very wrong - the debugger ends on the wrong line
(step into method from a class belonging to my GUI project in
Hi
@Xamarin team: I do not want to cross-post to MT list too much, but if
this is of interest
for MT developers, somebody from team pls cross-post it.
On 2012.08.17 11:53, Matthias wrote:
Hi,
I'm using some similar approach too but the problem is that you are losing
some part of the your to
Hi,
I'm using some similar approach too but the problem is that you are losing
some part of the your toolchain namely the ability to refactor code is
reduced. The different files (linked or not) are usually not seen as real
dependency so rename or so fails (correct me when I'm wrong but this happe
Hi Stephan
On 2012.08.17 10:52, Stephan Steiner wrote:
Craig, Mel
Thanks for your suggestions. I will try out the approach you suggested and
report back with my findings.
Thanks.
I forgot samples (with effort, just so You can have feeling):
* SharpSNMP (4 days, in WP project not clean (ifde
Craig, Mel
Thanks for your suggestions. I will try out the approach you suggested and
report back with my findings.
Stephan
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/Stepping-into-standard-NET-libs-tp5711361p5711370.html
Sent from the Mono for Android mail
Hi
On 2012.08.16 22:17, Stephan Steiner wrote:
Hi
I guess I'm missing something. I'm developing a mobile version of a client
that is already available on PCs in multiple forms. Those different clients
are meant to share as much code as possible in order to cut down on
repetitive work. So, there
Can you provide some more details on how you are sharing the code:
specifically are your Android projects just referencing a pre-built
assembly containing your shared code? You mention "built against .NET 4.0"
so i'm guessing this is the case?
I'm assuming you have the source code for those shared
Hi
I guess I'm missing something. I'm developing a mobile version of a client
that is already available on PCs in multiple forms. Those different clients
are meant to share as much code as possible in order to cut down on
repetitive work. So, there's a bunch of libraries that are to be shared
amon
20 matches
Mail list logo
