In Git you can add a submodule to a repository. This is basically a sub-repository embedded in your main repository. This can be very useful. A couple of usecases of submodules:
- Separate big codebases into multiple repositories.
| $userPath = $env:USERPROFILE | |
| $pathExclusions = New-Object System.Collections.ArrayList | |
| $processExclusions = New-Object System.Collections.ArrayList | |
| $pathExclusions.Add('C:\source\repos') > $null | |
| $pathExclusions.Add('C:\Windows\Microsoft.NET') > $null | |
| $pathExclusions.Add('C:\Windows\assembly') > $null | |
| $pathExclusions.Add($userPath + '\AppData\Local\Microsoft\VisualStudio') > $null | |
| $pathExclusions.Add($userPath + '\AppData\Local\Microsoft\VisualStudio Services') > $null | |
| $pathExclusions.Add($userPath + '\AppData\Local\GitCredentialManager') > $null |
| FROM microsoft/mssql-server-linux | |
| COPY . /usr/src/app | |
| ENTRYPOINT [ "/bin/bash", "/usr/src/app/docker-entrypoint.sh" ] | |
| CMD [ "/opt/mssql/bin/sqlservr" ] |
| function main { | |
| Update-Windows-Configuration | |
| Install-Utils | |
| Install-Browsers | |
| Install-Fonts |
| <?xml version="1.0" encoding="UTF-8"?> | |
| <meta-runner name="Cake"> | |
| <description>Execute a cake script</description> | |
| <settings> | |
| <parameters> | |
| <param name="mr.Cake.script" value="" spec="text description='The location of the Cake Script, relative to the root folder' display='normal' label='Cake Script:'" /> | |
| <param name="mr.Cake.target" value="" spec="text description='The name of the Target within the Cake Script to execute' display='normal' label='Target:'" /> | |
| <param name="mr.Cake.verbosity" value="" spec="select data_1='Quiet' data_3='Minimal' data_5='Normal' data_7='Verbose' data_9='Diagnostic' description='The logging level for the Cake Script' display='normal' label='Verbosity:'" /> | |
| <param name="mr.Cake.arguments" value="" spec="text description='Additional arguments to pass to Cake Script' display='normal' label='Cake Arguments:'" /> | |
| </parameters> |
| namespace Analogy | |
| { | |
| /// <summary> | |
| /// This example shows that a library that needs access to target .NET Standard 1.3 | |
| /// can only access APIs available in that .NET Standard. Even though similar the APIs exist on .NET | |
| /// Framework 4.5, it implements a version of .NET Standard that isn't compatible with the library. | |
| /// </summary>INetCoreApp10 | |
| class Example1 | |
| { | |
| public void Net45Application(INetFramework45 platform) |
| cmd /c ""C:\Program Files (x86)\Git\bin\bash.exe" --login -i -- H:\Daily_Reports\yesterdayTogglReport.sh" |
| # SERVER | |
| set :domain, "yago.webfactional.com" | |
| set :user, "yago" | |
| # NAME | |
| set :application, "yago" | |
| # REPOSITORY | |
| set :repository, "[email protected]:Yago31/yago-site.git" |
| <# | |
| .SYNOPSIS | |
| Converts files to the given encoding. | |
| Matches the include pattern recursively under the given path. | |
| .EXAMPLE | |
| Convert-FileEncoding -Include *.js -Path scripts -Encoding UTF8 | |
| #> | |
| function Convert-FileEncoding([string]$Include, [string]$Path, [string]$Encoding='UTF8') { | |
| $count = 0 |