Merge pull request #62 from spences10/update-readme

🎢add gifs yo!🎢

Author: mattpalermo

README.md

@@ -51,16 +51,27 @@ All you need to do to build the binary is create an empty `.zip` file, name it `
 
 >Now [I'm assuming you're on windows] if you have the Folder Options setting for `Hide extensions for known file types` checked then this is the time to uncheck it.
 
+![](/img/unhide-file-extensions.gif)
+
 Rename the file extension on the newly created `VBA-IDE-Code-Export.zip` file from `.zip` to `.xlsm` acknowledge the dialog saying `if you change the extension bad things might happen` and you will have the binary ready to add the code to.
 
+![](/img/build-from-source.gif)
+
 ### Add the code
 
 Best way to do this, have the `VBA-IDE-Code-Export.xlsm` VBA IDE open in one window then the file explorer open at the `src` folder in another window.
 
 Multi select the contents of the folder **_excluding `VBA-IDE-Code-Export.package` and `CodeExport.config.json`_** drag and drop into the `VBA-IDE-Code-Export.xlsm` VBA IDE.
 
+Add in the following references: 
+
+1. Microsoft Scripting Runtime
+2. Microsoft Visual Basic for Applications Extensibility 5.3
+
 Save, Debug>Compile the project then from the Immediate pane in the VBA IDE enter `auto_open` and hit return this should create the VBA IDE menu items, you're ready to move onto **usage.**
 
+![](/img/add-code.gif)
+
 ## Usage
 
 The add-in will create a menu in the VBA IDE (the VBE) called `Export for VCS`. All controls for the add-in are found in this menu.
@@ -83,7 +94,6 @@ The `Import` button in the `Export For VCS` menu will:
 * Add all library references declared in the configuration file. Existing library references will be overwritten.
 * Set the VBAProject name as declared in the configuration file.
 
-
 ### Exporting
 
 The `Export` button in the `Export For VCS` menu will: