You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, download files, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!
If you have any problems with the registration process or your account login, please contact contact us.
Microsoft Mobile and Embedded Application Developer Center has posted a writeup by Pete Vickers on how to port the eMbedded Visual Basic file controls to Visual Basic .NET when migrating Pocket PC applications. "Introduction
The next generation of Windows Mobile™-based devices will not support eVB applications. Developers will need to migrate their eVB applications to the new world of the Microsoft® .NET Compact Framework and Visual Basic®.NET. Windows Mobile 2003-based devices do not contain the eVB runtimes although they are available as an unsupported download. It is not possible to debug an eVB application running on Windows Mobile 2003-based Pocket PCs. For many developers, this transition provides an opportunity to revisit and update old applications. It also provides an opportunity to extend their applications to Windows Mobile 2003-based Smartphones which include the .NET Compact Framework in ROM.
This paper addresses how to replace the eVB File System and File controls in the Visual Basic .NET environment, using the System.IO namespace. When you start working with Visual Basic .NET, you'll get many new functions by using the System.IO namespace. For example, how many hoops do you have to jump through to find out whether a file exists in eVB?.. " via Activewin
Linear Mode
