Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I think its a rather simple question but I couldn’t really find an answer for it so I will ask it in case someone else might need it .
There are developers who in-order to copy all projects to bin folder set the bin folder path using the project output path property and there are developers who use the xcopy command in post build event.
What are the main reasons for it ?
Regards ,
James Roeiter
I think setting project output path is a better option. The reason is that in this case Visual Studio is in control: it takes care of cleaning up, replacing older files, deciding which files to copy… When using xcopy, Visual Studio just invokes blindly a batch file. It will run all the commands on the batch which will result in files being copied whether they were compiled or not. Also, if the compilation order of projects changes, or new projects are added or removed, the corresponding post-build actions need to be updated, resulting in extra steps.