Why there are two platform selections in EVC for only one SDK?

Similar Threads:

1.PPC 2002 Platform SDK for eVC 4.0 ???

Pocket PC 2002 SDK is only for eVC3

-- 
Andrey Yatsyk [Windows Embedded MVP]

"Nick" < XXXX@XXXXX.COM > wrote in message 
news: XXXX@XXXXX.COM ...
> Is there a PPC Platform 2002 SDK for eVC 4.0 ? I found it for PPC 2003 but
> not for PPC 2002?
>
> Thanks a lot,
>
> Nick 

2.Selecting Active WCE Platform (SDK)-PRB: eVC not responding (cpu 1

I've installed eVC 4.0 and updated to SP4, installed WCE 4.20 Standard SDK, 
another standard SDK (came with eVC?) and the OEM SDK I need that apppears as 
"Windows CE 4.20".  Active configuration is Win32 (WCE ARMV4I) Debug. Default 
device is "Windows CE 4.20 Device".

Using a new workspace and adding a new project, the SDK defaults to the 
Windows CE 4.20 Standard.  Everything appears to work fine, I can communicate 
with device using Tools, and build works up to the point where it tells me 
the standard does not match connected device platform.

When I try to change the active WCE platform to OEM SDK (or any other), eVC 
stops responding (hour glass cursor / cpu 100% utilized)

Device is Win CE 4.2.0 / StrongArm CPU.
-- 
JimC

3.eVC cannot connect to SDK from Platform Builder

I was using the eVC STANDARDSDK emulator but needed the parallel port
driver included, so I followed tutorial 8 from PB help files to brew
up an OS image and make it into an SDK for use with eVC.

When I use the SDK in eVC, eVC launches the emulator just fine (the
emulator's window appears), but eVC tries to connect for some goodly
time, but fails to connect.  

When I built the OS, I did not include KITL, since reading earlier
posts on this board indicating that KITL conflicts with the emulator
communication in eVC.

In "Configure Platform Manager" dialog, I selected "emulator startup
server" as the startup server.  The other selections in that drop-down
don't seem to work, either.

For Transport, I selected "TCP/IP Transport".

There must be something missing from the tutorial that I need to do
for the OS or SDK builds that will correct this problem, but I have
not been able to figure it out as yet.

Any help would be appreciated.

4.EVC++ 4.0, SP4, two SDKs - Tool commands lost on platform switch

I'm targeting multiple platforms, same CPU using a common code base.
Target 1 is a WinCE 4.1 build, target 2 is a 5.0 build.  Obviously,
each has their own SDK.  I have the project configurations established
to build each target and place it in a specific target directory.  All
is well ... sort of...

I noticed that when I switched SDKs, eVC++ had the wrong directories
for the tools under the Tools... menu.  So, I corrected the
directories.  However, when I change the SDK, I lose my corrected
entries.

What is the magic for getting eVC++ to retain the Tool settings?

5.SDKs for EVC/VS2008 - aka sdk he$$

I'm starting to work in an increasingly mixed mode of application
development.  On my backup development machine I have EVC 4.0 plus SP4
and VS2008 Professional.  I'm mostly native development, but I'm going
to begin dabbling in .Net (hence VS2008).  I'm comfortable with EVC
4.  I add a custom SDK, and it shows up.  Very predictable.

However, when I add an SDK for the Symbol MC1000 (I think I have the
correct one, I'm targetting WinCE 4.2), the SDK never appears as a
target in EVC.  This situation leads me to a clip from another
discussion earlier in October:

>On Oct 17, 1:45 am, "Michel Verhagen (eMVP)" < XXXX@XXXXX.COM > wrote:
> Yes, you can target CE 5.0 devices fromVisualStudio (05 or 08) just
> fine. Chris has been working on a native application, but you can also
> use VS for managed development targetted at CE 5.0 devices. No problem,
> *if* you have the right SDK for the device.
>

Michel - when you say "if" - are you referring to the fact that the
SDK must match the hardware, or is there some other subtle issue?

I have 5 Win CE targets installed: 2 custom targets for Win CE 4.2 and
5.0, Windows Mobile 5.0 for Pocket PC, Windows Mobile 5.0 for
Smartphone, and an SDK for a Symbol MC1000.

Now the SDKs are derived from an OS build targeting a specific slice
of h/w.  But is there anything in the SDK specific to an application
development tool?  For example, if my h/w vendor built an SDK for my
Win CE 5.0 target that works just fine with EVC 4.0, should it work
for VS 2008?

My understanding is that the SDKs should work with either - noting the
fact that the SDK is tied to the OS target.

thanks

6. best platform SDK and DirectX9 SDK compatible compiler

7. Can Switch do two things from One selection?

8. Why am I one of the few - I never ever receive any Spam