• This FAQ assumes you have Embedded Visual Basic 3.0 installed on your machine.
• If you are planning on using the emulator, you need to be running Windows NT 4.0 or Windows 2000.
• To make sure EVB and the emulator have been installed without problems, download this example EVB project, start EVB, load the project into EVB and try to run it on the emulator.
• If you get a message saying "No Such Interface Supported" when you load this project, then go to this article in the MSDN knowledgebase for directions about how to update your comcat.dll file.
• You might want to take a look at Microsoft's release notes for Embedded Visual Basic 3.0.

Some differences betwen Visual Basic 6.0 and Embedded Visual Basic:

• If you have a text box, it will ignore things like telling it to right-justify unless you set the multiline property to true.
• When attempting to work with substrings while in a form the function Right works, the function Mid works, but the function Left does not work. Any use of Left in an EVB form will refer to the property rather than the function. This is mentioned in the on-line help under Remarks thus teaching us the lesson to read those remarks!
• Control arrays are not supported. However, arrays of controls are allowed, so it might be possible to still do some of the things you would use a control array for in Visual Basic.
• When working with IrDA and Winsocks, the documentation implies that you can just set the ServiceName property rather than the port and be ready to go. However, what it overlooks is that you also need to have the remote host's name or IP. It would be nice if all PocketPC devices shared the same name, but they don't. For example, my Jornada is HP548 while my iPAQ is Pocket_PC. In general, it should be possible to have one device broadcast its name so others can find it. However, this does not appear to be an option from within the Winsock object itself (there are ways to do this using calls to external APIs - more details of this type of work-around to follow soon... One can also just directly access the IR port as a COM port, but different devices assign different COM port numbers to the IR port, so you'll need to read the port number out of the registry.