Merge pull request #703 from pascalberger/VbDoc

Add documentation about support of VB.NET

Author: gep13

docs/index.md

@@ -37,3 +37,14 @@ You can just run `GitVersion.exe` in your repository to see what variables are a
 There are two ways to consume GitVersion, the first is by running GitVersion.exe. The second is an MSBuild task. The MSBuild task is really easy to get up and running, simply install GitVersionTask from NuGet and it will integrate into your project and write out variables to your build server if it's running on one. The exe offers more options and works for not just .net projects.
 
 Read more about [using GitVersion](usage/usage.md)
+
+## Supported languages and frameworks
+GitVersion is language and framework agnostic.
+
+### Automatic update of version in projects
+GitVersion supports the following projects to automatically update its version information.
+
+| ProjectType                           | Command Line Tool           | MS Build Task  |
+| :------------------------------------ | :-------------------------- | :------------- |
+| C# Project with `AssemblyInfo.cs`     | Supported                   | Supported      |
+| VB.NET Project with `AssemblyInfo.vb` | Supported                   | Not supported  |

docs/usage/command-line.md

@@ -15,13 +15,13 @@ By default GitVersion returns a json object to stdout containing all the [variab
 `GitVersion.exe /output buildserver` will change the mode of GitVersion to write out the variables to whatever build server it is running in. You can then use those variables in your build scripts or run different tools to create versioned NuGet packages or whatever you would like to do. See [build servers](../build-server-support/build-server-support.md) for more information about this.
 
 ## Inject version metadata into the assembly
-`GitVersion.exe /updateassemblyinfo` will recursively search for all `AssemblyInfo.cs` files in the git repo and update them. 
+`GitVersion.exe /updateassemblyinfo` will recursively search for all `AssemblyInfo.cs` or `AssemblyInfo.vb` files in the git repo and update them. 
 It will update the following assembly attributes:
 
 * `AssemblyVersion` will be set to the `AssemblySemVer` variable.
 * `AssemblyFileVersion` will be set to the `MajorMinorPatch` variable with a appended `.0`.
 * `AssemblyInformationalVersion` will be set to the `InformationalVersion` variable.
 
-Note that contrary to when using the [MSBuild Task](msbuild-task.md) the attributes must already exist in the `AssemblyInfo.cs` files prior to calling GitVersion.
+Note that contrary to when using the [MSBuild Task](msbuild-task.md) the attributes must already exist in the `AssemblyInfo.cs` or `AssemblyInfo.vb` files prior to calling GitVersion.
 
 By adding `/updateassemblyinfofilename` the name of AssemblyInfo file to update can be set.