New version of CF...

  • Thread starter Thread starter Isaque Briglia Gonçalves
  • Start date Start date
I

Isaque Briglia Gonçalves

Hi to all,

When the new CF will be avaliable.
The current CF graphic is very slow:
form title filcker, controls in tabs freeze,
lines, rectangles and etc is to slow, etc...

Why this topics are not present in eVB or eVC.

The "new" tecnologie are too slow than "older" tecnologie.

Maybe the "new" is the "older" delayed... Maybe...

I'm very frustrated with this...

The marketing say in 2002: "New tecnologie... More fast and robust..." <-
Where ???

Sorry by my confiance in marketing.
 
I don't think you want to paint both eVC and eVB with the same brush. Since
eVC generates actual machine code for the target processor, it will usually
generate code that is faster for a given operation than any other tool.
This is to be expected.

My experience is that eVB is very slow at most things. The only aspect of
..NET CF programs which seems slower than eVB to me is initial load of the
application, which is also to be expected, given that the .NET CF program is
actually being compiled, effectively, at that point.

The speed advantage that many of us see in .NET CF programming is on the
development side. That is, it's a lot faster to write an application,
particularly one that uses Web services, in .NET CF than it is in eVC. You
also only have to compile it once, not for each separate processor
architecture that you want to support, as you must with eVC. This might
also save you on testing, since, at least in theory, you only have to test
one EXE with .NET CF, but one per processor for eVC.

If you can't live with the run-time speed, switch to eVC. That's what it's
there for...

Paul T.
 
Back
Top