Comments by Babak Mahmoudi (Top 9 by date)

Why CREO cannot use C++\CLI, is probably because the exported functions have dual entries (i.e they have both managed and native). Try exporting pure native entries with '#pragma managed' directive. I'm sure you can eliminate the C++ dll in your solution.

DLLs are loaded from the directory where the main executable is loaded, not the working directory, so I think you should place the DLLs in C:\Y, where CREO.exe is located or use some other way to influence the DLL seach, such as locating dlls in assembly cache. (See http://msdn.microsoft.com/en-us/library/windows/desktop/ms682586(v=vs.85).aspx#search_order_for_desktop_applications for more details on Dll Search Mechanism)

I dont think Cygwin has any influence in the problem.
By the way, there is an ILMERGE tool that can merge two assemblies in one. It's a great tool, but I really wonder if it can Merge a mixed (C++/CLI) assembly with a pure one. Nevertheless there's still a way to merge the C# layer with the C++ layer (http://blogs.msdn.com/b/texblog/archive/2007/04/05/linking-native-c-into-c-applications.aspx), this way you would only have a single DLL, which can be registered as a plugin and assuming all other refrenced assemblies are system assemblies and located in the Assembly Cache you'll get a neat solution with less dependencies.

It seems that "kmbds.dll" is using some other dll(s) that are not accessible. Try to copy any other dll that may be used by kmbds, to your application folder. You may use "Depends.exe" to check kmbds.dll dependencies on other dlls.