You will have to declare it with something like this (I'm no eVB expert and I haven't tested this):
Public Declare Function CopyFile Lib "Coredll" Alias "CopyFileW" (ByVal ExistingFileName As String, ByVal NewFileName As String, ByVal FailIfExists As Bool)
See the help file on the Declare statement. Regards, João Paulo
theJazzyBrain wrote: What developer web sites would you suggest other than CP which is good but not focused on Pocket PC dev... Try The Pocket PC Developer's Network[^] theJazzyBrain wrote: Basic question is, what versions of Windows for Pocket PC support the Compact .NET framework? I'm not sure about the original Pocket PC, but you will find support for the .NET Compact Framework on the Pocket PC 2002 (in RAM) and 2003 (in ROM). If you are going down the .NET CF way, find yourself a fast machine... ;) theJazzyBrain wrote: and aplogies for my ignorance on Pocket PC development... We are all born ignorant. The ones that die that way never asked questions, or never had the chance to. ;) Regards, João Paulo
Hi Dave, To get the selected portion of the text, you use the EM_GETSEL message or, if using MFC, CEdit::GetSel. These will return indexes to the starting and ending characters of the selected substring. To retrieve the full string, use GetWindowText. Regards, João Paulo
Find the adoce31.tlb file and make the #import directive point there. If you do not have this file on your PC, download it from Microsoft Website (search for ADOCE 3.1) and install it. Regards, João Paulo
rodent¹ wrote: additionally, ppc2k or ppc2k2 apps SHOULD run on ppc2k3 From my experience (limited :)) this is the case. rodent¹ wrote: if you want to develop for ppc2k or ppc2k2 devices you must use evc++3.0 This seems to be true. For now I am going to stick with EVC++3.0, as for the time being I will only be developing for PPC2k2. Thanks for the response :-D Paul ;)
Garfield.Bark(); **---Configuration: garfield - Win32 Deworm---** C:\garfield.cpp(9) : error C2039: 'Bark' : is not a member of 'CCat'
For #1: The linker supplied with eVC will remove unused packages (called COMDATs in the documentation) if the /OPT:REF switch is turned on. This is turned on by default, unless the /DEBUG switch is enabled, in which case it's turned off. To force the linker to remove unreferenced functions, the compiler must be instructed to package each function in its own COMDAT. You do this by specifying the /Gy option to the compiler (called 'Enable function-level linking' in the 'Customize' category of the Project Settings dialog). If this option is not enabled, the linker can only include or exclude individual object files. A static library basically consists of multiple object files with a header describing what's in it. From memory, Microsoft's static libraries are compiled with this option enabled.
thanks Steve and it makes sense...i'll check out WINNT.H on my system for the #defines you mention. what's frustrating me is that i haven't found out why the resource compiler is even including afxres.h in the resource includes when i purposely create the project as a non-MFC project and don't utilize the wizard-created files. i'll check out what you suggest as well as continue to dig into the compiler/linker/other options in hope of finding this.