Updated Readme.MD and the comment based help

Author: martin9700

README.md

@@ -38,6 +38,11 @@
 	as PSModuleBuild will read in all .ps1 files and put them in but if you'd like to make sure these commands are run at
 	the beginning of the file you can.
 
+	Public/Private Functions
+	========================
+	PSModuleBuild will support public and private functions as well.  In your project folder create a Public folder and a Private 
+	folder and place your function files appropriately.  
+	
 
 #EXAMPLES
 	Simple
@@ -73,7 +78,8 @@
 	--------------------------------------
 	If you have about files, or additional XML descriptor files, PSModuleBuild will support that.  First create a project folder,
 	then create a source folder and place all of your function files in there.  Now create another folder with the name of your
-	module (we'll use NewModule in this example) and place all of your files in them in the proper folder structure.
+	module (we'll use NewModule in this example) and place your about files, and other files there, in the proper folder structure
+	(en-US, etc).
 
 	$BuildSplat = @{
 	   Path = "c:\ProjectFolder\Source"   
@@ -104,6 +110,24 @@
 	   Passthru = $true
 	}
 	Invoke-PSModuleBuild @BuildSplat
+	
+	
+	Advanced - Mulitple Target Paths
+	--------------------------------
+	Need to deploy the module to multiple paths?  Maybe you have a primary production location but also a process running
+	in a DMZ?
+	
+	$BuildSplat = @{
+	   Path = "c:\ProjectFolder\NewModule\Source"   
+	   TargetPath = "c:\ProjectFolder\NewModule","\\dmzserver\share\Modules\NewModule"    #this is optional now, Invoke-PSModuleBuild goes here by default
+	   ModuleName = "NewModule"
+	   Author = "@thesurlyadm1n"
+	   Description = "This is that new module I've been working on"
+	   ProjectURI = "https://github.com/martin9700/PSModuleBuild"
+	   ReleaseNotes = (git log -1 --pretty=%s) | Out-String   #Pull release notes from your git commits
+	   Passthru = $true
+	}
+	Invoke-PSModuleBuild @BuildSplat
 
 
 #SEE ALSO

Source/Invoke-PSModuleBuild.ps1

@@ -17,6 +17,12 @@ Function Invoke-PSModuleBuild {
             ^build\.ps1$
             \.psdeploy\.
 
+        Public and private functions are also support by creating the proper folder structure:
+
+        \Source
+           \Public
+           \Private
+
         If you have any scripts or cmdlets that need to be run at Import-Module time, you can put them in an Include.txt
         file and PSModuleBuild will read this file first and put it in the module file first.  This is not strictly needed
         as PSModuleBuild will read in all .ps1 files and put them in but if you'd like to make sure these commands are run at
@@ -27,7 +33,9 @@ Function Invoke-PSModuleBuild {
         The path where you module folders and PS1 files containing your functions is located.
 
     .PARAMETER TargetPath
-        The path where you want the module and manifest files to be located. If it does not exist Invoke-PSModuleBuild will create it.
+        The path where you want the module and manifest files to be located. If the folder does not exist Invoke-PSModuleBuild will create it, if
+        it is not designated it will use the Path location.  Multiple folder paths can be designated as well if you want to deploy to multiple
+        locations.
 
     .PARAMETER ModuleName
         What you want to call your module. By default the module will be named after the folder you point
@@ -79,6 +87,7 @@ Function Invoke-PSModuleBuild {
         1.0.13          Removed a debugging line.
         1.0.14          Rename to Invoke-PSModuleBuild and create module named PSModuleBuild.  Added ReleaseNotes support (New and Update-ModuleManifest treat ReleaseNotes differently)
         1.0.15          Updated comment based help
+        1.1             Added multiple target paths
     .LINK
         https://github.com/martin9700/PSModuleBuild
     #>