Ways of packaging up a custom DLL with 3rd Party exe

I'm curious to know how to wrap up some 3rd party exe files into my dll for deployment.

At the moment we rely on the deployed system having the 3rd party software installed and our wrapper exposes their console app to our MVC application.

Ideally I'd like the wrapper and the exe's all packaged up together in a nice bundle that can be deployed anywhere regardless of the 3rd party app being ins开发者_StackOverflow中文版talled.

Any advice on where to store the exe files in my application would also be really helpful. I'm curently dropping them into the bin.

I'm aware that licencing can be an issue here and it's something I'm already ontop of.

---

By "packaging" you mean including the .exe file in your dll? I mean you could of course include the .exe file into your setup package, but that's not what you want if I understand correctly.

I believe starting a .exe file which does not physically exist ist not possible in windows. But you could include the .exe file as a ressource into your .dll.... possibly in a compressed form. When you need it, it could be dropped into a temporary directory, executed, and deleted after use or on dll uninitialization.

However this technique could maybe alert some security software...