OK, I can see when I open it that it's a list of dependencies (for an old COM DLL). But how do I use that information in .NET world?
We're working on a VS2008 setup and deploy project to deploy some Winforms software.
We're including in the project an old COM DLL (which comes with a .DEP file).
The documentation which comes with the DLL says our installation package should copy and register the DLL on the target PC. The DLL is automatically recognised by VS2008 as a dependency and it's my understanding that the default VS2008 setup and deployment project takes care of the copy and register stuff.
The documentation also says the Interop.xxx.dll has to be distributed too, and I see that VS2008 has automatically created that and included in the setup project and I guess is taking care of that.
Finally the documentation says there's a .DEP file to assist us (there is) and it says a .NET application needs to distribute the "VB6 runtime and associated DLLs" There's six dependencies. VS2008 certainly hasn't added them automatically to its setup project. Do I need to do it manually?