If this has been asked elsewhere, please direct me. When I search for solutions I get nothing but questions on automating Visual Studio builds or tasks with batch scripts.
I'm using VS2010 Pro and moving to VS2012 Pro.
We manage our web sites as VS Projects or web site.
We manage our batch VB code with VS Projects - but mostly just include items pertaining to the EXE and its execution. We do not include the corresponding batch scripts to run the EXE since these are often shared with other EXEs.
We have a \Runtime suite of folders to manage our batch scripts and other control files. We currently use a varity of editors including VS and even Notepad at times. This is not as automated as we want because TFS points to our local drive and the Runtime code is not easy to code, test, deploy locally so it must be copied to server to test adequately. What occurs is version issues because people get lazy and edit server version directly and TFS is not always updated.
Is there a way to add a new project type that I can point to Runtime and have it expect file types of CMD, SQL, TXT, VBS to automatically include and manage?
Ideally when we say "build" we would like all modified files to be copied to similar folder structure on our development server for real execution and testing.
This would facilitate our easily checking files in and out, maintain current code both locally and where it is actually tested properly on server.
I have built an External Tool batch script to copy files one by one as I edit & save them, but it is not quite as robust.
We cannot be the only ones wanting this capability. I'm thinking I just haven't found the right search string.
Oh, adding color coding to batch files would just be a great bonus. Most tools I've used manage it with a specially named file containg lists of reserved words, comment identifiers and color choices to use.