Merge pull request #9 from pezhore/master

Module refactor, Automated Testing, bundled libaries

.gitattributes

@@ -15,3 +15,22 @@
 *.PDF	 diff=astextplain
 *.rtf	 diff=astextplain
 *.RTF	 diff=astextplain
+
+# Explicitly declare text files we want to always be normalized and converted
+# to native line endings on checkout.
+*.md            text
+*.gitattributes text
+
+# Declare files that will always have CRLF line endings on checkout.
+*.ps1    text  eol=crlf
+*.psm1   text  eol=crlf
+*.psd1   text  eol=crlf
+*.psc1   text  eol=crlf
+*.ps1xml text  eol=crlf
+*.clixml text  eol=crlf
+*.xml    text  eol=crlf
+*.txt    text  eol=crlf
+
+# Denote all files that are truly binary and should not be mergeable.
+*.dll binary
+*.exe binary

Documentation.adoc → Legacy_Documentation.adoc

@@ -501,4 +501,3 @@ YAML also has a rather crude way of allowing you to represent relational data by
 I find YAML to be very useful. What really convinces me of the power of YAML is to be able to walk the representational model to do special-purpose jobs such as processing hierarchical data to load into SQL. It is at that point that I finally decided that YAML had a lot going for it as a format of data document. 
 
 
-

PSDeploy/PSYaml.PSDeploy.ps1

@@ -0,0 +1,17 @@
+# Specify Module Name
+$ModuleName = "PSYaml"
+
+# Determine our installation path based on where "My Documents" is located
+$InstallPath = $env:PSModulePath.split(";") | Where-Object {$_ -match "My Documents" -or $_ -match "Documents"}
+
+# Specify deploy task
+Deploy "Install $ModuleName" {
+    By Filesystem {
+        FromSource $ModuleName
+        To "$($InstallPath)\$($ModuleName)"
+        WithOptions @{
+                        # This overrides any existing content
+                        Mirror = $True
+                     }
+    }
+}