Dll dependecies

[kevin]

Hi All,
I have a shell app that uses an API function found in MPD.dll. I wanted
to add this dll to my shell component as a component dependency, but
could not find it in the database. So I ran mpr.dll through Depends and
got a list of 28 other dll dependencies. I then added all of these dll's
to my shell compenent and built the image. This gave me BSOD 0x00000071
shortly after the Windows splash screen, so I don't think I took the
right approach to the problem. What is the correct way of getting all
dendency dll's into my components?
thanks
kevin

 

[Gordon Smith \(eMVP\)]

Hi All,
I have a shell app that uses an API function found in MPD.dll. I
wanted to add this dll to my shell component as a component
dependency, but could not find it in the database. So I ran mpr.dll
through Depends and got a list of 28 other dll dependencies. I then
added all of these dll's to my shell compenent and built the image.
This gave me BSOD 0x00000071 shortly after the Windows splash screen,
so I don't think I took the right approach to the problem. What is
the correct way of getting all dendency dll's into my components?
thanks
kevin

The correct approach is to find the DLLs you need. In your case, MPD.dll.
Then use a filter to find the component which contains the DLL you care
about. Those DLLs (even if in the windows repositories) aren't always
contained in a component. If it exists in a windows repository and isn't
referred to by a component, you can create a component which refers to that
DLL. If it's a DLL that isn't in the windows repositories, then treat it as
a 3rd party file (many articles on third party integration).

 

[KM]

kevin,

Just to clarify, MPR.dll ("Primitive: Mpr" component) or MPD.dll (there is no such on XP Pro/ XPe) ?

The correct approach would be including system components that include the Dlls you found with the DependencyWalker. Utilize TD
Filter feature to search for all the components by file names that contain.