Your opinion on .NET CF

[Natalia]

Hi,
Those of you who has worked with .NET CF for a while,
I need your opinion.

.NET CF is only a beta now, but how is it working? Do you
experience any troubles with it? It is quite usual that
quality of beta products is not always the best one...
We have to choose if we will develop an PPC application
using Embedded Visual Basic or .NET. I've read that Visual
Basic.Net is much more powerfull than Embedded Visual
Basic, but I haven't had any possibility to
test it yet, as Smart Device Extensions is not available
for download any more. I'm quite sure that language is
better, but how about the framework?
Are there any conflicts, lack of resources, anything else
that does not work yet?

So, I would appreciate your opinion on .NET CF.

/Natalia

[Maarten Struys]

Be aware that only VS.NET 2003 is in beta. The .NET CF that is part of the
final beta of VS.NET 2003 is actually the RTM version. So far my own
experiences with the .NET CF are positive. I am using it for evaluation
purposes, mainly programming in C#. Sometimes I read comments in this
newsgroup about performance issues but I have not experienced performance
problems myself.

You have to keep in mind that the .NET CF is a .NET Framework subset, so not
all functionality of the .NET Framework is available, but still, the .NET CF
is a rich, powerful environment. I would like to see (lots of) documentation
improvements.

The decision to use eVB or VB.NET: Well, as far as I know there are no new
versions of eVB scheduled. So if you want to develop PPC applications that
will also run on future PPC's with Windows CE.NET as underlying OS, you
might need to switch to eVC or one of the .NET languages anyway. I am not
forcing a decision for you, but perhaps making one easier.

Regards,
Maarten Struys
PTS Software bv

"Natalia" <natalia...@trustlink.com> wrote in message
news:039601c2d1c8$a23b87f0$a301...@phx.gbl...

[Dom]

Go with .NET. We've all had a moan about certain things missing /
performance issues with XScale etc but .NET is seriously an absolutely
awesome product. What's more converting code from mobile to desktop is an
absolute breeze. I coded with eVB from the beginning and it was all about
"work arounds". .NET is the future. Whilst excellent at the time eVB is over
and a dead end. Go with .NET. You won't regret it. Finally I've been coding
12 hours a day since RTM came out and it hasn't crashed ONCE !
Warm regards and good look on your adventure in .NET
Dom
"Maarten Struys" <maarten...@nospam.pts.nl> wrote in message
news:#QZRpAf0CHA.616@TK2MSFTNGP11...

[Ginny Caughey [MVP]]

Natalia,

I think you will be pleased with the .NetCF. I believe that VB.Net will
completely replace eVB for future versions of Windows CE, so getting started
with .NetCF now puts you on the long-distance track. The main feature that is
missing in the current version of .NetCF compared with eVB is support for COM,
and there are several workaround approaches including a third party library that
is in development.
--
Ginny Caughey
Windows Embedded MVP

"Natalia" <natalia...@trustlink.com> wrote in message
news:039601c2d1c8$a23b87f0$a301...@phx.gbl...