Shaun Luttin shaunluttin
davidfowl
/ Example1.cs
Last active
September 2, 2024 12:36
How .NET Standard relates to .NET Platforms
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 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) |
glombard
/ Get-ScriptPath.ps1
Created
May 2, 2014 10:45
Use different techniques to determine a PowerShell script's directory: try `$PSScriptRoot`, `$MyInvocation.MyCommand.Path`, `$ExecutionContext.SessionState.Module.Path` and `$PWD`.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| function Get-ScriptPath { | |
| $scritDir = Get-Variable PSScriptRoot -ErrorAction SilentlyContinue | ForEach-Object { $_.Value } | |
| if (!$scriptDir) { | |
| if ($MyInvocation.MyCommand.Path) { | |
| $scriptDir = Split-Path $MyInvocation.MyCommand.Path -Parent | |
| } | |
| } | |
| if (!$scriptDir) { | |
| if ($ExecutionContext.SessionState.Module.Path) { | |
| $scriptDir = Split-Path (Split-Path $ExecutionContext.SessionState.Module.Path) |