what is the differences/limitations between vs2003 and vs2008 fordeveloping mobile application

[evgininanir]

hi ,
i am a new developer in mobile development and software development..
can anybody give me a direction about differences between vs2003 and
vs2008? or links to find out exactly this.
because i made a lot of searching for this at msdn and did not find
things enough to go on...
anyway our development envoirement is vs2003 (c#) and we want to
upgrade to vs2008 (c#)...
thanks for answering...i am really confussed...

 

[Fabien]

Hi,

With VS2008, you could use Compact Framwork 3.5.

BR

Fabien Decret (Device Application Development MVP)
Windows Embedded Consultant

ADENEO (ADESET)
http://www.adeneo.adetelgroup.com/ | http://fabdecret.blogspot.com/

 

[evgininanir]

thanks ,
but my point is to find out the differences between these 2 platform
for developing smart device applications....
is there a site or a book that you can suggest me..

thanks again...
Evgin

 

[Paul G. Tobey [eMVP]]

No, there's no book on the differences between two versions of Visual Studio
(talk about a limited market!) VS.NET 2003 only supports development of
..NET Compact Framework 1.0 applications. VS 2005 supports both .NET CF 1.0
and 2.0 applications. Generally, if you are going to target 2.0, you want
2005 and, if 1.0, you want 2003. What's the real point of the question?

Paul T.

 

[evgininanir]

thank you Paul for your answer ...
the real point is we developed a cf project in vs 2003 ... and we
want to update it to vs 2008 .
before we do that i want to find the difference's between these two
platforms....
and also we developed for ppc2003 se now we have to update to wm5.0
and later edition like wm6.0 and so what will be nezt
editions...anyway some samples of my problems :
in our project we use rda object to transfer data between
sqlserver2000 and sqlce2.0 ,
we use sqlce2.0 ------- will i have to update it sqlce3.5 ?
for serialport communication opennetcf components , and e.t.c.
will i have to do a lot of things to make it work ?

thank you again...
evgin

 

[Paul G. Tobey [eMVP]]

Well, the only way you're going to go to VS2008 is to change the target .NET
CF version of your project. You can't build a .NET CF 1.0 project in
VS2008, as far as I understand it. If your target is .NET CF 1.0, because
it's globally available in some generation of devices, then you should stay
with your current development environment.

Yes, if you change .NET CF versions, you *will* have to upgrade the database
to the later version (which is why our devices continue to include .NET CF
1.0, and not 2.0, in them). This is the biggest of the issues, in my
opinion. Since you're using a remote database as the primary data source
and just using RDA to get the data, it's not that big a deal. The
underlying database on the device side will just be different than the one
on used before.

As for SerialPort, .NET CF 2.0 has its own serial class. It's essentially
compatible with the OpenNETCF one (and appears to me to have been defined
based on the OpenNETCF class model), so that's not much of a porting issue.

Paul T.

 

[Simon Hart [MVP]]

I have written a blog entry describing whats new in CF 3.5 and VS 2008 for
device developers, although this was aimed at developers moving from CF 2.0
VS 2005 to CF 3.5 VS 2008 but it will give you a good overview of what to
expect.

I have written a blog which explains converting your CF project to CF 3.5
here:
http://simonrhart.blogspot.com/2008/02/upgrading-your-solutions-to-visual.html

You can still continue to use SQL CE 2.0 with VS 2008, you just won't be
able to use any of the built-in data tools and will have to reference the
assembly's manually. A requirement is CF 1.0. If you run this on a Pocket
2003 SE or later CF 1.0 comes installed in ROM. WM 6 CF 2.0 comes installed
in ROM. In this case you'll need to install CF 1.0 if you plane to use SQL CE
2.0 on WM 6 devices.

--
Simon Hart
Visual Developer - Device Application Development MVP
http://simonrhart.blogspot.com

 

[Daniel Moth]

[importance=low]

compatible with the OpenNETCF one (and appears to me to have been defined
based on the OpenNETCF class model), so that's not much of a porting
issue.

It is actually the other way round When I implemented the serialport for
the SDF I based it on the interface of the Beta desktop serialport (which of
course is interface compatible with what ended up in the NETCF version).

Cheers
Daniel