Best way to implement a wrapper class with files

[Christopher Stratmann]

Lets say I have a old executable that was not created in the .NET world that contains a bunch of dll and stuff like that. This old executable takes in command line arguments to generate a specific result. I was thinking about creating a .NET assembly class to wrap this executable. The programmer using this wrapper would be able to specify certain properties and then generate a result. My question is simple. When deploying this wrapper assembly do I........ 1. Store the old executable and dlls into the assemblies Resources.resx and when the user wishes to generate a result make a directory and copy the files into the directory (if they do not already exist) and then generate the result. 2. Attach the old executable and dlls into a folder within the assembly project itself and change the build action to content and when the project is deployed make sure the content files are also deployed with the project. 3. Use another method? Thanks Chris

[Colin Angus Mackay]

chris175 wrote:

2. Attach the old executable and dlls into a folder within the assembly project itself and change the build action to content and when the project is deployed make sure the content files are also deployed with the project.

That is the option I'd go for. It keeps the app with its DLLs in a known place relative to your application.

---

Upcoming events: * Glasgow: Mock Objects, SQL Server CLR Integration, Reporting Services, db4o, Dependency Injection with Spring ... "I wouldn't say boo to a goose. I'm not a coward, I just realise that it would be largely pointless." My website

[Christopher Stratmann]

Thanks for the input.