Do you work on projects in Visual Studio? Are you looking for a free and simple way to source control your projects without sharing them with the whole world? Would you like to be able to manage your projects online and still be able to work on your projects offline? If so, you may want to look into using Visual Studio and Git.
As a speaker and blogger, I create projects for demos, videos and screenshots. When I only had a few projects it worked quite well to “source control” my projects: I kept them in a OneDrive folder, created copies of demo code for new presentations and maintained versions manually.
However, the projects grew in number and size and became more difficult to maintain. There were no easy ways to track how I changed and improved my code over time, and I couldn’t revert to previous code. I kept telling everyone else to use source control, so I decided it was finally time to source control my personal projects.
In this post I will show you how I added my first project to source control with Visual Studio and Git.
The schedule looks great! I’m a little sad that Sonja Chèvre (@SonjaChevre) is speaking at the same time as me, because I really want to see her present. We met at SQLSaturday Oslo 2015, and I’m so happy to see that she is now speaking! Hopefully I’ll get to attend one of her sessions at another event :)
If you want to chat, have any Biml questions, or want me to go through some of the content from my more advanced Biml sessions – I will be available the whole day. Make sure you register now so you don’t end up on a wait list, and join the conversation on Twitter by using the hashtag #SQLSatVienna.
Do you use C#/VB classes and methods in your Biml projects? One solution is to create class nuggets <#+ … #>, but they can only be used in their containing Biml file. You can move class nuggets to separate files and include those files, but a more elegant solution is to use C#/VB Code Files.
In addition to using C#/VB Code Files, there are four other main ways you can avoid repeating your Biml code:
Is it March yet? I’m very happy to announce that I will be speaking at SQLSaturday Chicago 2016! A huge thank you to the organizers who selected my session :D
This will be my first trip in 2016, and I’m really looking forward to visiting a new city. It’s going to be a long trip for just a few days, but it will definitely be worth it!
On Saturday, March 5th, I will present my Biml for Beginners: Speed up your SSIS development session. It’s an introduction to Biml for those who are just starting to learn Biml. I have presented this session at a few events now, and I always find something to improve. Some content will be familiar for those who have seen my slide decks already, but I’m currently working on a few tweaks.
I will be available the whole day if you want to chat, have any Biml questions, or want me to go through some of the content from my more advanced Biml sessions. I’m slightly obsessed with the topic, and I’m happy to talk for hours if someone doesn’t stop me ;)
Take a look at the amazing schedule, register now so you don’t end up on a wait list, and join the conversation on Twitter by using the hashtag #SQLSatChi.
Are you using Biml so you won’t have to do the same tasks over and over and over again in multiple SSIS packages? If so, you probably don’t want to write the same Biml code over and over and over again either. Instead, you can move common code to separate files, centralize and reuse these files in many projects, and update code in one file to make changes to all projects. One of the ways to apply this Don’t Repeat Yourself software engineering principle in Biml is to use Include Files.
In addition to using Include Files, there are four other main ways you can avoid repeating your Biml code: