|
Posted by CN99 on December 28, 2005, 2:30 am
Please log in for more thread options
Hi all:
I started a VC/SmartDevice project under VC 7.0, But the CFile class seems
don't works, I wonder is it because of the specific project I choose?
The innocent statement like:
CFile file;
if ( ! file.Open( _T("C:\Test.txt", CFile::modeRead ) )
{
return;
}
is always invalid, the if statement always evaluate to TRUE
I wonder is there's some inherent problem?
|
|
Posted by Ilya Tumanov [MS] on December 28, 2005, 3:15 pm
Please log in for more thread options
If by VC 7 you mean VS 2003, it does not support C++ for devices, C# and
VB.Net only.
If you mean single language products, they have no device support at all.
Also, devices don't have drive letters in path.
Best regards,
Ilya
This posting is provided "AS IS" with no warranties, and confers no rights.
*** Want to find answers instantly? Here's how... ***
1. Go to
http://groups-beta.google.com/group/microsoft.public.dotnet.framework.compactframework?hl=en
2. Type your question in the text box near "Search this group" button.
3. Hit "Search this group" button.
4. Read answer(s).
show/hide quoted text
> Hi all:
> I started a VC/SmartDevice project under VC 7.0, But the CFile class seems
> don't works, I wonder is it because of the specific project I choose?
> The innocent statement like:
> CFile file;
> if ( ! file.Open( _T("C:\Test.txt", CFile::modeRead ) )
> {
> return;
> }
> is always invalid, the if statement always evaluate to TRUE
> I wonder is there's some inherent problem?
>
|
|
Posted by CN99 on December 28, 2005, 8:11 pm
Please log in for more thread options
show/hide quoted text
> If by VC 7 you mean VS 2003, it does not support C++ for devices, C# and
> VB.Net only.
By VC 7.0 I mean VS 2005
show/hide quoted text
> If you mean single language products, they have no device support at all.
> Also, devices don't have drive letters in path.
My target device is "Pocket PC 2003 SE Emulator". So the program is running
on desktop PC. But the problem still remains.
|
|
Posted by Ilya Tumanov [MS] on December 28, 2005, 8:59 pm
Please log in for more thread options I see... Yes, VS 2005 (sometimes considered to be version 8) indeed supports
native C++ for devices.
If your target is emulator, your program is not running on desktop; it's
running on emulated Pocket PC.
VS 2005 emulator emulates not only Windows CE environment, but also ARM
processor and other PPC hardware as well.
File system is also emulated and is independent from desktop's file system.
There's no direct mapping between files visible in emulator to files on your
desktop's drive.
You can, however, map any folder on your PC into simulated storage card of
emulator.
So, to fix this issue, please copy this file "Test.txt" to emulator (via
Active Sync, for example).
Also, please change the path so it would be correct for emulator, e.g.
"\Test.txt" if file is located in the root folder of the emulator.
Best regards,
Ilya
This posting is provided "AS IS" with no warranties, and confers no rights.
*** Want to find answers instantly? Here's how... ***
1. Go to
http://groups-beta.google.com/group/microsoft.public.dotnet.framework.compactframework?hl=en
2. Type your question in the text box near "Search this group" button.
3. Hit "Search this group" button.
4. Read answer(s).
show/hide quoted text
>> If by VC 7 you mean VS 2003, it does not support C++ for devices, C# and
>> VB.Net only.
> By VC 7.0 I mean VS 2005
>> If you mean single language products, they have no device support at all.
>> Also, devices don't have drive letters in path.
> My target device is "Pocket PC 2003 SE Emulator". So the program is
> running on desktop PC. But the problem still remains.
>
|
|
Posted by CN99 on December 28, 2005, 10:24 pm
Please log in for more thread options
写入消息新闻:43b34306$1@news.microsoft.com...
show/hide quoted text
>I see... Yes, VS 2005 (sometimes considered to be version 8) indeed
>supports native C++ for devices.
> If your target is emulator, your program is not running on desktop; it's
> running on emulated Pocket PC.
> VS 2005 emulator emulates not only Windows CE environment, but also ARM
> processor and other PPC hardware as well.
> File system is also emulated and is independent from desktop's file
> system.
> There's no direct mapping between files visible in emulator to files on
> your desktop's drive.
> You can, however, map any folder on your PC into simulated storage card of
> emulator.
> So, to fix this issue, please copy this file "Test.txt" to emulator (via
> Active Sync, for example).
> Also, please change the path so it would be correct for emulator, e.g.
> "\Test.txt" if file is located in the root folder of the emulator.
> Best regards,
> Ilya
Well, Thanks a lot, I'm new to emmbedded world, your answer gives me a feel
on it.
Regarding "...So, to fix this issue, please copy this file "Test.txt" to
emulator (via
Active Sync, for example..."
That solve the problem if "Test.txt" is already exists. But how to go about
when you want to create a file?
|
| Similar Threads | Posted | | Bug In Smart Device Installer Project | March 1, 2007, 11:16 am |
| Unable to create Win32 Smart device project using VS 2005 | July 27, 2006, 8:34 am |
| Maintain project dir structure on device after compiling? | October 17, 2005, 10:27 am |
| Smart Device Template Missing | December 2, 2006, 7:06 am |
| Detect 3G/2G networking in smart device | September 28, 2007, 2:01 am |
| Smart Phone 2002 - OS problem | September 29, 2005, 5:18 am |
| ANN: OpenNETCF.org Smart Device Framework v1.4 Released | August 5, 2005, 4:14 pm |
| [ANN] OpenNETCF Smart Device Framework 2.0 Beta1 | January 30, 2006, 4:55 pm |
| How can I specify Unsupported Platforms in a Smart Device CAB Proj | April 5, 2007, 2:10 pm |
| how to set clr option for smart device win32 application | June 5, 2007, 8:07 am |
|
> I started a VC/SmartDevice project under VC 7.0, But the CFile class seems
> don't works, I wonder is it because of the specific project I choose?
> The innocent statement like:
> CFile file;
> if ( ! file.Open( _T("C:\Test.txt", CFile::modeRead ) )
> {
> return;
> }
> is always invalid, the if statement always evaluate to TRUE
> I wonder is there's some inherent problem?
>