The following software will need to be installed locally in order to proceed: So how can this work in VS Code, on a personal laptop? Let's work it through with an example! There are many flavours / variations of / extensions to the above, but this is the general approach. Create a Pull Request (also known as a Merge Request)Īt this point the change is reviewed, and - assuming it looks good and the tests are passing - the green button is clicked and an automated pipeline will deploy the project to the server and update the documentation.Commit changes (perhaps using the conventional commit standard).Apply standardised code styles (linting).The traditional way to use GIT in software development, is for each developer to have their own local clone of a shared code repository - where they can:

This last point is key for those with a background in GIT workflows. Ability to compile and execute SAS projects locally, without impacting other developers.Vast marketplace with third party extensions.For more information on how this framework ( SASjs) can accelerate the development, deployment, quality checking, testing and documentation for Data Engineering projects - read on!īut first - why VS Code? We say it is a great choice of IDE for SAS Developers, for the following reasons:

There is a VS Code marketplace though, and over the last 12 months my colleagues in the SAS Apps team at Analytium have been hard at work building an open source framework for SAS DevOps that fits nicely into an extension. This is a true testament to the great work by SAS R&D, supported by the fact that third party editors like VS Code do not ship with any SAS functionality.

According to github data, Visual Studio Code is the third most popular IDE in the world - whilst this linkedin poll shows that 90% of SAS developers actually prefer Base SAS, Enterprise Guide or SAS Studio.

Git in visual studio code