Database Reference
In-Depth Information
Organizing and invoking scripts (Medium)
In this recipe we will look at organizing script code into multiple script iles for better
reusability and maintainability.
Getting ready
Complete previous recipes irst. Use the sample code iles included with this recipe or create
them manually in the same directory, copying code from the samples as needed.
How to do it...
1.
Create Oracle.DataAccess.ps1 for common ODP.NET code. Some examples
from this ile included with this recipe's sample code are as follows:
function Get-ODPAssemblyName
{
param ( [Parameter(Mandatory=$true)][validateset(2,4)]
[int] $version)
$a = @{}
$a["2"] = "Oracle.DataAccess, Version=2.112.3.0,
Culture=neutral, PublicKeyToken=89b483f429c47342"
$a["4"] = "Oracle.DataAccess, Version=4.112.3.0,
Culture=neutral, PublicKeyToken=89b483f429c47342"
$a[$version.ToString()]
}
function Get-ODPAssembly
{
[appdomain]::currentdomain.getassemblies() `
| ? {$_.FullName -like 'Oracle.DataAccess,*'} `
| select -first 1
}
function Load-ODP
{
param (
[Parameter(Position=0, Mandatory=$true)]
[validateset(2,4)]
[int] $version,
[Parameter(Position=1)]
[switch] $passThru
)
$asm = [System.Reflection.Assembly]::Load((Get-ODPAssemblyName
 
Search WWH ::




Custom Search