|
Posted by ctacke/ on September 7, 2007, 10:18 pm
Please log in for more thread options
> 1: Does anyone know of the default DLLs (or SYSGENs) that *must* be in
> *all*
> Windows Mobile 5.0 devices, versus optional DLLs which *may* be present,
> versus DLLs that will *not* be present?
This would be covered under the WM NDA.
> 2: Relating to this question: If Windows Mobile 5 does *not* come with a
> SYSGEN, and therefore related DLLs, is it possible for a Windows Mobile 5
> software vendor to use PB 5 to generate the missing SYSGEN, and related
> DLLs,
> and then include some, if not all of the DLLs, for redistribution with the
> WM5 application?
A SYSGEN is an environment variable, not something that is "created".
Having them set causes creation/inclusion of features whan a build is done.
Generally speaking for CE any components created with PB are to be
distributed only with a CE image, not as separate DLLs (there are some
exceptions with LIBs and headers exported with an SDK).
> 3: If this is not generally acceptable, how can one contact Microsoft to
> find out how to be an exception, or how to obtain redist info for a
> particular Microsoft DLL that is not normally a part of WM5?
A good question. Which DLL(s) are you specifically looking at? Some of us
may be able to ask around, but I'd need to know exactly which files and what
the case/need is for distribution outside of a device. My guess is the
answer will be "no" as just having a DLL doesn't mean it will work on
another device. Often support for a DLL must also get linked into other
parts of the system, like coredll.dll - it's not just a matter of
distributing a DLL.
--
Chris Tacke, Embedded MVP
OpenNETCF Consulting
Managed Code in an Embedded World
www.OpenNETCF.com
| 
XML Sitemap