Re: adding XML support (without new OS image)

From: John Spaith [MS] (jspaith_at_ONLINE.microsoft.com)
Date: 09/27/04 

Date: Mon, 27 Sep 2004 12:37:16 -0700

There's 2 fronts you need to investigate this on. The first is the
technical, which I can do my best to help with. The other is legal, as far
as whether you can redistribute components on existing images or not. I
personally don't have any problems if you do this. Remember however that
John==Engineer, John!=Microsoft Legal Department :). I'd talk with your
technical accounts manager about this and they can get you the definitive
answer.

In theory an image built without MSXML3 can have it added after the fact.
As you already realize, the underlying OS has to have all the required
components for MSXML in order for this to work. First off you'll need all
the registry settings for msxml3.dll. These can be found in ie.reg of an
image that you've created to get msxml3.dll bits in the first place.

After that, I'd focus on making sure that MSXML3.dll not having the required
OS support is your problem. Write a small app that just does a
LoadLibrary("msxml3.dll") and see if it succeeds or if it fails. If it
suceeds, then it would look like msxml3 dll being not setup right isn't the
problem. Maybe the registry is incorrect or there's something wrong in your
test app? If this fails, first see if the error code returned makes it
obvious what the problem is. If not, if possible create a debug version of
the OS image that you're targeting and a debug msxml3.dll. Then in Platform
Builder turn on nk.exe's debug zone for the loader. This should tell you
exactly which function or functions the linker is missing when trying to do
the load if this is the problem.

Let me know how this works out and if there's anything else I can help with
once you try the steps above. 

-- 
John Spaith
Software Design Engineer, Windows CE
Microsoft Corporation
Check out the new CE Networking Team Blog at http://blogs.msdn.com/cenet/.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2003 Microsoft Corporation. All rights 
reserved.
"jj3000" <jeremy_ho@my-deja.com> wrote in message 
news:3ed9e158.0409270920.4addc983@posting.google.com...
> We already have our systems deployed and running CE.NET 4.1 out there,
> but during the time the CE.NET OS was built without XML support.
>
> We have an CE application it would run on the new OS image (that I
> built with XML support, along with ATL).   But when tried to run on
> the original OS image, it will say it is "not a valid CE application".
>
> I have tried to copy EVERY DLL that is new to the new OS (msxml3.dll,
> etc) over to the same directory of our application, but it doesn't
> help any.
>
> Is there anyway to make the old OS image support XML without deploying
> a whole new OS image.  Or find out precisely what is our application
> is looking for a specific setting or DLL.   I have already ran dumpbin
> but can't find anything specific, my guess is the msxml3.dll needs
> some other things.
>
> Also I have noticed the coredll.dll is different sizes on both images.

Relevant Pages

  • adding XML support (without new OS image)
    ... but during the time the CE.NET OS was built without XML support. ... I have tried to copy EVERY DLL that is new to the new OS (msxml3.dll, ... Also I have noticed the coredll.dll is different sizes on both images. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Windows CE 5.0 bug list
    ... I've managed to get the vmini.dll built by including the Local Area Netowork ... I've read the article and I am in the process of tracing through how the DLL ... " The output of the BSP phase is normally placed in a CPU-specific directory ...
    (microsoft.public.windowsce.platbuilder)
  • dll Release or Debug?
    ... Is there any way to tell if a dll that was built was built in debug or ... and we think it might be because this dll was build incorrect. ... Brent ...
    (microsoft.public.dotnet.general)
  • Re: What reference should I add, Debug or Release?
    ... >> When I'm adding a reference to another project that is built as one of ... should I add the dll in Debug or the one in ... I have to delete the reference and add it once again. ... > automatically use the debug or release build of that dll depending on ...
    (microsoft.public.dotnet.languages.csharp)