.NET CF does not support latebound overload resolution?

  • Thread starter Thread starter C.K.
  • Start date Start date
C

C.K.

bytes = System.Text.ASCIIEncoding.ASCII.GetBytes(send1) ' send is STRING

Hello, I am writing the above line of code and I am receiving the
following error from the syntax-hint system:

..NET CF does not support latebound overload resolution

I was wondering if someone can explain what is latebound
resolution, why is the line above considered latebound
resolution, and what can I do to obtain bytes instead of
a STRING ?

Tia
 
Alex Feinman said:
It's
bytes = System.Text.Encoding.ASCII.GetBytes(send1)

Using ASCIIEncoding.ASCII should work just as well though - I agree
it's far from nice stylistically, but I don't think that's the problem.
 
bytes = System.Text.ASCIIEncoding.ASCII.GetBytes(send1) ' send is STRING

Hello, I am writing the above line of code and I am receiving the
following error from the syntax-hint system:

.NET CF does not support latebound overload resolution

I was wondering if someone can explain what is latebound
resolution, why is the line above considered latebound
resolution, and what can I do to obtain bytes instead of
a STRING ?

Could you post a short but complete program which demonstrates the
problem?

See http://www.pobox.com/~skeet/csharp/complete.html for details of
what I mean by that.
 
I forgot to dim 'send' as string, my mistake. I did
dim send ="aaa" instead of
dim send as string="aaa"
Thanks for the help.
 
I forgot to dim 'send' as string, my mistake. I did
dim send ="aaa" instead of
dim send as string="aaa"

The way to avoid this being a problem is to use Option Strict On, I
believe (although I'm far from a VB.NET expert).
 
Thanks, I will use it, loose typing is terrible, for me, this option should
be on by default.
:)
 
Thanks, I will use it, loose typing is terrible, for me, this option should
be on by default.

Likewise. Strong typing is the desired behaviour in almost all
situations, as far as I can see...
 
Back
Top