Database Reference
In-Depth Information
Exploring ODT assemblies (Advanced)
This recipe will explore use of the Oracle.Management.Omo assembly included with Oracle
Developer Tools for Visual Studio (ODT). This assembly is intended for internal use within
Visual Studio so you will not ind documentation or support for it and any code you write
against it may break upon future ODT updates. Even so, this Oracle .NET library provides
such rich functionality that these drawbacks may be acceptable.
Getting ready
You will need ODT installed; see the recipe Setup Your Environment . You will need to be able
to load .NET 4.0 assemblies from PowerShell. See the Loading ODP.NET 4.0 section in the
Accessing Oracle (Simple) recipe for more.
How to do it...
1.
Load the Oracle.Management.Omo assembly:
PS > $odtAsmName = "Oracle.Management.Omo, Version=4.112.3.0,
Culture=neutral, PublicKeyToken=89b483f429c47342"
PS > $asm = [Reflection.Assembly]::Load($odtAsmName)
2.
Look at the types in the assembly that start with " Con ":
PS > $types = $asm.GetTypes() | ? {$_.IsPublic}
PS > $types | ? {$_.Name -like 'Con*'} | sort {$_.FullName } | ft
-auto FullName
FullName
--------
Oracle.Management.Omo.ConnectAs
Oracle.Management.Omo.Connection
Oracle.Management.Omo.ConstraintBase
Oracle.Management.Omo.ConstraintCollection
Oracle.Management.Omo.ConstraintInitialState
Oracle.Management.Omo.ConstraintType
 
Search WWH ::




Custom Search