Sorry if there was a more appropriate place to post this question. Feel free to redirect me.
We have an extensive set of perl scripts (program.pl) that are scheduled and executed from cmd files in the background on a network drive (i.e. no user interface).
We want to convert these to c# scripts written/deployed if possible from our Studio 2010 environment.
My first attempt was to create a Console Application and suppress the console popup. It's a simple script that reads data and produces emails. It all works fine - but the Studio Publish process was not as straight forward as I had hoped. I'd rather not have a setup.exe process to execute and all of the application objects associated with it. We are just wanting a simple script deployed to a network location and execute from a cmd file.
Question - is this the best method to write/deploy c# batch/background scripts? Did I perhaps Publish incorrectly? Any advice would be appreciated.
We have an extensive set of perl scripts (program.pl) that are scheduled and executed from cmd files in the background on a network drive (i.e. no user interface).
We want to convert these to c# scripts written/deployed if possible from our Studio 2010 environment.
My first attempt was to create a Console Application and suppress the console popup. It's a simple script that reads data and produces emails. It all works fine - but the Studio Publish process was not as straight forward as I had hoped. I'd rather not have a setup.exe process to execute and all of the application objects associated with it. We are just wanting a simple script deployed to a network location and execute from a cmd file.
Question - is this the best method to write/deploy c# batch/background scripts? Did I perhaps Publish incorrectly? Any advice would be appreciated.