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 created a console app that I want to use in a scheduled package in SSIS. In the app, I’m connecting to the database to get email addresses and sending emails to that list. When I put the .exe on the server it won’t work, but when I put the whole folder over, it works fine. I’m assuming it needs the app.config.
What’s the best way to deploy the exe to the server? Should I publish the console app first, or just build it and take the exe and the app.config (not sure if that’s possible)?
Copying whole Bin folder is perfectly valid way of deploying files (sometimes called x-copy deployment).
There could be other files in Bin folder (i.e. referenced assemblies that you marked as “copy” in the project).
You can build more formal install package, but it most likely overkill for simple scenarios.