Correctly deploying a CS app with DLLs

[aVoX]

Hello!
I want to build Crystal Space with DLLs for the sake of easier updating of the final result. But when I tried a testing application on another computer, i found out that simply copying of crystalspace-2.0-vc100.dll into the directory of the executable doesn't work. Basically the application needs crystalspace-2.0-vc100.dll, libz-cs.dll, engine.dll, and vfs.dll but it also needs the DLLs of all plugins used.
Is there somehow a way to avoid a DLL nest like this (except static linking)? Otherwise the configurations ReleaseWithDlls/DebugWithDlls would be pretty pointless and updating an app would be heck of a work.

Thanks in advance,
aVoX.

[res]

Well, there's a middle ground between having all plugins as (separate) DLLs and static linking everything into one executable: you can have the plugins your app needs built into a single DLL.

If you want to see how this looks like, open the “wksstatic” solution and build walktest_static, but in one of the  “with DLLs” mode. If you check the dependencies of walktest_static.exe with Dependency Walker (or some similar tool), you'll see it depends on the standard crystalspace* DLLs and one “plugins” DLL (into which basically all the plugins were built).