How would a .NET Smart Device port help us. What OS does a .NET Smart Device sit on? XP embedded (XPe)?
Main Topics
Browse All TopicsI need to port a VB6 app over to windows CE. Currently, we run the app under W2000 and XP. We are migrating to an embedded version running on Windows CE. How difficult is this (I have zero experience with CE) - ie how much recoding? 10%, 90%? The app is a basic GUI and file I/O stuff.
The app currently relies on a DLL for some RS232 I/0. Can CE run Windows 2000/XP DLLs? Or can we also look forward to recoding the DLL?
Thanks.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I believe the .NET Smart Device Extensions support even the older PocketPc OSes...not completely sure though.
The only reason I suggested it is because there are utilities that are supposed to convert old VB6 programs to VB.NET syntax. They're not perfect, but they may be sufficient enough to save you time from doing a complete rewrite. Then, once its into its VB.NET form, it is in much better position to move to the SDE environment since they utilize the same development environment and language. Old eVB is basically VBScript, plus if you use any APIs, all those must be ported to the handheld API, if there is even a similar one.
yes emebedded visual basic(eVB) is rather limiting, depending on what your application uses(ie what controls you have on the form etc), the minimum you will need to allow for is 50-80% recode. infact just about anything outside of algorithms and functions (Excluding those that uses API) needs to be recoded
Business Accounts
Answer for Membership
by: AzraSoundPosted on 2006-11-03 at 18:15:00ID: 17871558
It can be pretty difficult considering the differences in code. Any Windows ocxs/dlls that you rely upon are not going to be available to you on CE. So, yes, you would need to recode your RS232 dll.
It may actually be easier to port your code to a .NET Windows application, and then port that over to a .NET Smart Device application.