Work with Pocket PC 2002

[apex1x]

What would be the best way to develop a PPC 2002 program? Is it possible with VS.NET 2005? If there is an existing 2005 application originally built for PPC 5.0, would it be possible to convert?

 

[ThatRickGuy]

Not sure on 2k5, but I developed an app for a PPC 2002 PDA in VS.Net 2k2/2k3. You have to use the compact frame work, which can make things a bit more interesting, but all in all, it's not all that different from making a standard windows app.

-Rick

VB.Net Forum forum796 forum855 ASP.NET Forum
I believe in killer coding ninja monkeys.

 

[jebenson]

From the .NET 2.0 Compact Framework download page:

* Supported Operating Systems: Windows CE .NET; Windows Mobile 2003 software for Pocket PCs

* Supported Device Operating Systems: Windows Mobile Software for Pocket PC 2003, Windows Mobile 5.0 for PocketPC and Smartphone, Windows CE .NET 5.0 and higher.

So it looks like the answer is no, you can't develop for PPC 2002, but you can for PPC 2003.



I used to rock and roll every night and party every day. Then it was every other day. Now I'm lucky if I can find 30 minutes a week in which to get funky. - Homer Simpson

Arrrr, mateys! Ye needs ta be preparin' yerselves fer Talk Like a Pirate Day! Ye has a choice: talk like a pira

 

[apex1x]

Ok, I'll see if I can get VS.NET 2003...
It seems strange though you can't develop PPC 2002 apps on VS.NET 2005. Is there any SDK or anything for this? From what I've seen, they're only for Embedded Visual Basic... Hmm..
Suggestions?

 

[ThatRickGuy]

You CAN make a PPC 2002 app in VS.Net 2005. You can't make that app using the version 2 of the .Net Framework. Some place in the solution options (right click on the solution in the solution explorer, and select options) you should be able to select what version of the framework you want to use. Switch it to Compact Framework 1.0 and you should be good to go.

-Rick

VB.Net Forum forum796 forum855 ASP.NET Forum
I believe in killer coding ninja monkeys.

 

[apex1x]

Could you go into a bit more detail in selecting the 1.0 framework?
Are you talking about changing "target platform"? Changing "references"?
Do I need to download/add anything or should this be available by default? Thanks.

 

[ThatRickGuy]

I'm not sure, I still haven't gotten around to installing 2k5. In 2k3 if you right click on the solution and select "Configuration Manager" you should see a list of the projects in the solution. Change the "Platform" field to the correct version of .Net.

You'll probably have to have v1.1 of the .Net framework and the v1.0 compact framework installed. both should be available on MS's site.

-Rick

VB.Net Forum forum796 forum855 ASP.NET Forum
I believe in killer coding ninja monkeys.

 

[tperri]

As far as I know, the previous Pocket PC 2002 and 2003 releases are included in the .Net 2.0 compact framework, so there is no need to install the SDKs as you had to do when working in VS 2002 and 2003

 

[apex1x]

I just got VS.NET 2003 and now I'm able to work with Pocket PC 2002 devices. It looks as if I will need to hard code everything, as design time databinding looks out of the question.

I'll see if I can search for some sites to do this. Any suggestions on working with SQL Mobile CE and synching with an SQL 2005 database?

 

[ThatRickGuy]

minimize network traffic, avoid hard number crunching, and play with other approaches for optimization.

I have a PPC2002 application that downloads TV schedules, displays a listing, and links up with a Windows MCE box to change the channel, volume and set record schedules.

One of the roughest parts was getting the TV Schedules downloaded and displayed acceptably. We wound up using a web service that would strip the schedule information from XML (5 megs+) to coma delimited text stream (~450k). The text stream was manually read and parsed (loading the same data from XML took about 2 1/2 minutes, from CVS it took about 20 seconds), then loaded into a DataSet. Once the data was in a dataset we could use the datatable.select method to return a sorted, but not filtered array of data rows. We then flipped through the data rows and added them to an array list which we used to filter what we needed. The filtered list was then added back into a datatable. It sounds crazy, but it took our page swaping times from ~2seconds+ to under .4 seconds.

-Rick

VB.Net Forum forum796 forum855 ASP.NET Forum
I believe in killer coding ninja monkeys.