or others, I would be happy for more hints/tips on using Team Foundation Server (TFS) for SAS source code management.
I'm just about to start playing with it (don't have access yet). Happy to hear you endorse it, I was thinking it might be painful since the main client is Visual Studio.
Assume the simple case of a directory full of .sas files that want to have version controlled. Do you create a visual studio project that has links to those .sas files (and perhaps other file types, such as compiled formats and templates), and then do check-in and check-out through visual studio? Or does your SAS code end up living inside a Visual Project file (doesn't seem like that would really be an option)? Or do you perhaps use this TFS windows explorer extension to do check-in and check-outs, like you could with TortoiseSVN?
We will still be developing our code in DM SAS or EG or notepad or whatever, with .sas files sitting on a server. So curious at a simple level how much you have to change your work flow as a SAS developer to integrate with TFS.
Was at a SAS conference a while back and the pitch for TortoiseSVN was that from the SAS developer perspective, it made version control easy...
Thanks,
--Q.
BASUG is hosting
free webinars Next up:
Jane Eslinger presenting PROC REPORT and the ODS EXCEL destination on Mar 27 at noon ET. Register now at the Boston Area SAS Users Group event page:
https://www.basug.org/events.