CEC vs. project

From: "J Garcia" <jggarcia@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 29 Jun 2005 15:11:28 -0400

I've seen information (in our case - a DLL) built and included into an image
in 2 different ways - 1. A project was created and added as a user feature,
and 2. through inclusion via the catalog (CEC).

Both seemt to work. What are the pros/cons of doing it either way? Do (or
can) they both give the same end result? I suspect that with the catalog,
don't have to explicitely create a new project to use the feature in a new
platform. But what about other pros/cons?

.

Follow-Ups:
- Re: CEC vs. project
  - From: Steve Maillet \(eMVP\)

Prev by Date: RE: NDIS hanging during Init
Next by Date: Help PostMessage Delay
Previous by thread: NDIS DPC/ISR running in same thread in CE 5.0
Next by thread: Re: CEC vs. project
Index(es):
- Date
- Thread

Relevant Pages

Re: Adding features doesnt work
... Device drivers from the catalog were not showing up ... It seems that PB tries to determine if a feature is ... relevant for your project after you add it from the catalog. ... Either define a MODULE_NAME variable in the CEC as the target file name ...
(microsoft.public.windowsce.platbuilder)
Re: Problems in adding a driver in BSP
... in the catalog under my BSP in Third Party. ... You may want to open the CEC file that you created in the CEC Editor. ... the catalog to be displayed with your driver in bold. ...
(microsoft.public.windowsce.platbuilder)
Re: creating a new component
... what do you mean with 'new FMD'? ... If you've got a catalog file for this new FMD you must import it in ... if you want the item to appear under the BSP tree in the catalog you have to ... modify the BSP .cec file ...
(microsoft.public.windowsce.platbuilder)