about CPU processor type

  • Thread starter Thread starter dotnet[nothing]
  • Start date Start date
D

dotnet[nothing]

Before I use vs.net2003,I try eVc3.
When I use eVC3,I need select CPU type,e.g:ARM,x86.I don't find the option
on vs.net2003 now.
Please help me,and thanks.
 
You don't need to. DotNet assemblies are MSIL code which is an intermediate
language that is independent of the underlying architecture (ARM, SH3, X86,
etc.). This code will get Just-In-Time compiled by the Common Language
Runtime when you run the application on the target device. It is at this
point that the code is compiled to the native (architecture dependent) form.

So the bottom line is that you don't really need to worry about this with
..Net. You just need to distribute the correct Compact Framework CAB file
when you install the application. But when deploying through VS.Net 2003
this is taken care of for you.
 
Thanks for Wilson's helps.
I need distribute the correct Compact Framework CAB file.Where is it?
When the machine use ARM CPU,which file do I use?
When the machine use Xscale,which file do I use?
Thanks.
 
<VS.Net 2003 install location>\CompactFrameworkSDK\v1.0.5000\Windows
CE\wce300\arm\netcf.core.ppc3.ARM.cab

XScale is based on ARM so you use the same CAB file.
 
Thanks for Wilson's helps.

I have understood,and thanks.
please answer the following question:
I don't know user's ppc os is ppc2002 or wince.net,Do I need make two
Click to expand...
release version?
 
The Pocket PC configuration in Visual Studio supports all Pocket PC devices
whether 2000/2002/2003 so you don't need to know the OS version as long as
you know it is a ppc.

If you want to support generic Windows CE.NET devices as well as Pocket PC,
you can build your project using the Windows CE.NET configuration in VS.NET
and target all .NETCF supported platforms. You will then need to either add
code to layout your UI controls at runtime based on the screen size (using
the Screen object). Or separate your UI code into a separate assembly. That
way you can code a single codebase for all your program logic then provide a
very thin UI layer on top which is specific to a particular device type.

Peter

--
Peter Foot
Windows Embedded MVP

In The Hand
http://www.inthehand.com
Handheld Interactive Reference Guides
 
Back
Top