I am working on a VS solution that utilizes the post-build events to copy files into a deployment project that packages the files. Does anyone know if there is any best practice in how to move files around to place in an MSI?
Asked
Active
Viewed 732 times
2
-
Why not use a deployment project? – John Saunders Dec 06 '09 at 07:14
-
@John Saunders That is what is being used - all the prjects are using post-build events to copy the files into the deployment project. – Eric Dec 06 '09 at 07:19
2 Answers
0
As long as you copy all the dlls, exes, help files, icon files, resources ( but not .pdb), you are OK.
Why no pdb? Because pdb is debugging file, and it is there for debugging purpose. So in your release build, you don't need to have them.
Graviton
- 81,782
- 146
- 424
- 602
0
As long as you are sure that you never want something else that the latest release build in your package, you are fine. But if you want to be prepared for "repackaging" scenarios, for example, to have an option for easily exchanging a single file in an existing package, you should consider to separate the build process from the "copy to the deployment project" process.
Doc Brown
- 19,739
- 7
- 52
- 88