Does CE.NET support DirectX?

[MooreMao]

Dear all:
Does CE.NET support DirectX?
It seems eVC 4.0 can NOT develop DirectX.
Any plugins SDK?
So that I can develop DirectX with eVC 4.0??

Thank you.

[Eric Cosky]

I would very much like to learn how to use eVC 4.0 to
create a simple DirectX app of any kind. I have pored
over MSDN literally overnight trying to find how to do
it.. It would seem the headers are present in the eVC
distribution (ie. C:\Program Files\Windows CE Tools\wce400
\STANDARDSDK\Include\Emulator\ddraw.h is there, along
with all the other DX files) but what seems to be lacking
are the various .lib files, such as ddraw.lib

Any feedback on this would be greatly appreciated as I am
considering investing much time developing DirectX games
on CE.Net and I really need the DDraw support. Thanks!

>.
>

[Gary Daniels]

Yes, CE.NET does support directx, however it has to be added to the
platform, it's listed in Platform Builder under multimedia. For DirectDraw
you must have a DirectDraw enabled display driver. For Direct3D you must
have a DirectDraw and Direct3D enabled display driver.

I havn't used eVC, but i'm told that once it has been added to the platform
eVC should be able to use a Platform Builder generated SDK directory. I'm
going to try it myself sometime later today or tomorrow.

Gary
--
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2001 Microsoft Corporation. All rights
reserved.

"Eric Cosky" <er...@cosky.com> wrote in message
news:1f3801c234a6$c22c64e0$2ae2...@phx.gbl...

[Marcus Ash [MS]]

Eric:

The reason that you are not finding the appropriate libraries is due to the
fact that you need an SDK for whatever device you are planning to target.
If you are just interested in general CE application development, I would
recommend downloading the Windows CE.NET emulation edition. You can build a
platform for the emulator that includes the DirectX technologies you are
interested in, create an SDK, and develop and debug your application with
the tools provided in the emulation edition or import the SDK into eVC to do
your development work.

You can find the emulation edition at:
http://msdn.microsoft.com/downloads/sample.asp?url=/msdn-files/027/001/699/m
sdncompositedoc.xml&frame=true

Hope this helps.
--

Marcus Ash - marcashATmicrosoft.com
Lead Program Manager
Windows CE

--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Gary Daniels" <gar...@microsoft.com> wrote in message
news:uHI2uFNNCHA.1940@tkmsftngp11...

[Eric Cosky]

Thanks for the excellent tips, they pointed me in a direction that helped me
understand quite a lot more about what is going on here..

I have two follow up questions if someone could be so kind to help, followed
by some related comments which might affect the answers:

----------------
The Questions:

1. What target platform *should* I target if I want my application to be
able to be run on the latest crop of PocketPC's available today? (ie.
Toshiba e740)

2. Which development environment is most suited for developing for that
platform - Embedded Tools 3.0, Embedded Visual C 4.0, or the Windows CE.Net
Platform builder? I have *no* preference, I just want to most efficient tool
for the job. Ideally, this means, click "Build" and produce binaries ready
to test on several types of PocketPCs as a result.

------------------
Comments about my situation are below. Thanks for any feedback !

I was able to build a platform that included the DirectX stuff, which
produced the DX related .LIB files which although I haven't tested writing a
Windows CE DirectX app I think it's safe to assume this is probably what I
needed.

I am somewhat confused about a related issue however - I was hoping to write
apps for Pocket PC 2002, yet the platforms the builder creates are always
the Windows CE .Net versions. This is probably a dumb question, but is CE
.Net considered the successor to PocketPC 2002? If so, then this makes sense
for the latest dev kit to make CE.Net platforms, but if this isn't the case
then it seems odd to have to go back to CE Tools 3.0 in order to target
PocketPC 2002.

Part of my confusion is due to when I use the "Configure Platform Manager"
menu item in eVC 4.0, I am only able to see the platforms "STANDARD SDK
Emulator" and "Windows CE .Net Default Platform". I am pretty sure these
aren't what I want - I am under the impression PocketPC 2002 is the latest
target platform. When I run the various tools (ie. Remote System
Information) I get a list of a lot more platforms in the "Select a Windows
CE Device" dialog that comes up. In particular, I can select the PocketPC
2002 Emulator and get what appears to be the spiffiest version of the
emulator to start up.

Thanks again for the input

Eric Cosky

"Marcus Ash [MS]" <mar...@anti-spam.microsoft.com> wrote in message
news:ebKSRxONCHA.2712@tkmsftngp12...

[Steve Maillet (eMVP)]

See comments inline with yours below

--
Steve Maillet (eMVP - Windows CE)
Entelechy Consulting
smaillet_EntelechyConsulting_Com

"Eric Cosky" <ericATcosky.com> wrote in message
news:eiVafbrOCHA.2556@tkmsftngp10...

> 1. What target platform *should* I target if I want my application
to be
> able to be run on the latest crop of PocketPC's available today?
(ie.
> Toshiba e740)
>

Pocket PC 2002

> 2. Which development environment is most suited for developing for
that
> platform - Embedded Tools 3.0, Embedded Visual C 4.0, or the Windows
CE.Net
> Platform builder? I have *no* preference, I just want to most
efficient tool
> for the job. Ideally, this means, click "Build" and produce binaries
ready
> to test on several types of PocketPCs as a result.
>

eVC 3.0 and eVB 3.0 are the ONLY options for that platform from
Microsoft. Platform Builder is exclusively for creating custom
devices if you are the hardware vendor.

[...]

> I am somewhat confused about a related issue however - I was hoping
to write
> apps for Pocket PC 2002, yet the platforms the builder creates are
always
> the Windows CE .Net versions. This is probably a dumb question, but
is CE
> .Net considered the successor to PocketPC 2002? If so, then this
makes sense
> for the latest dev kit to make CE.Net platforms, but if this isn't
the case
> then it seems odd to have to go back to CE Tools 3.0 in order to
target
> PocketPC 2002.
>

Windows CE.NET is not the succesor to Pocket PC 2002. Windows CE.NET
is the succesor to Windows CE V3.0 Pocket PC 2002 is a Microsoft
defined *platform* that is built on top of the Windows CE V3.0
*Operating System*. Microsoft has not yet defined a Pocket PC platform
based on Windows CE.NET. In other words Windows CE.NET is Windows CE
V4.0 that marketting decided to put the ".NET" onto because everything
else at Microsoft was putting ".NET" on the name so, what the heck
let's join the crowd.

> Part of my confusion is due to when I use the "Configure Platform
Manager"
> menu item in eVC 4.0, I am only able to see the platforms "STANDARD
SDK
> Emulator" and "Windows CE .Net Default Platform". I am pretty sure
these
> aren't what I want -

No they aren't - you can't use eVC 4.0 with any device not using the
Windows CE.NET OS

> I am under the impression PocketPC 2002 is the latest
> target platform.

Depends on what you call the latest. There's a difference between the
OS and a platform. The Pocket PC is a platform and it's latest version
is based on Windows CE V3.0 and requires teh V3.0 tools.

> When I run the various tools (ie. Remote System
> Information) I get a list of a lot more platforms in the "Select a
Windows
> CE Device" dialog that comes up. In particular, I can select the
PocketPC
> 2002 Emulator and get what appears to be the spiffiest version of
the
> emulator to start up.
>

The emulator comes as part ot the Microsoft provided Pocket PC 2002
SDK

It would seem that you are trying to write DirectX applications for
Pocket PC devices. This cannot be done as the Pocket PC platform does
not include the DirectX support.

So I recommend you un-install Windows CE.ENT and eVC 4.0 to save disk
space and further confusion and then look into the GAPI functions in
the Pocket PC 2002 SDK.

[Eric Cosky]

Thank you very much for answering many of my questions, some I didn't know I
had yet :)

At the end you replied:

>It would seem that you are trying to write DirectX applications for
>Pocket PC devices. This cannot be done as the Pocket PC platform does
>not include the DirectX support.

>So I recommend you un-install Windows CE.ENT and eVC 4.0 to save disk
>space and further confusion and then look into the GAPI functions in
>the Pocket PC 2002 SDK.

Yes this was pretty much the idea originally based on a false impression
that DirectX support was available on PocketPC 2002. When I had seen GAPI
mentioned elsewhere, I had the impression it was being replaced by DirectX
on PocketPC which appears not to be the case - thus I will begin
researching how to use GAPI instead of DirectX. Thankfully, my code is not
really tied to DirectX for a couple of reasons so in the end this should be
pretty viable solution.

Thanks again for the great info

Eric Cosky

"Steve Maillet (eMVP)" <nos...@EntelechyConsulting.com> wrote in message
news:#4WLd68OCHA.1636@tkmsftngp13...