# powerVault v19

## v19.0.9

`24-04-2018`

- Official Release

**Features**

- powerVault [cmdlets](</code_reference/commandlets>) can be used in every IDE

**General**

- Updated to PowerShell 4.0
- Removed *powerVault ISE* shortcut from startmenu
- Assembly *coolOrange.VaultServices\_\[Vault Version\]* gets installed into the GAC

## v19.0.5beta

`12-03-2018`

**Fixed**

- [Get-VaultFileBOM](</code_reference/commandlets/get-vaultfilebom>) with arguments *-GetChildrenBy* [LatestVersion](<code_reference/commandlets/get-vaultfilebom:bomrowversiontype>), [LatestReleasedVersion](<code_reference/commandlets/get-vaultfilebom:bomrowversiontype>) and [LatestReleasedVersionOfRevision](<code_reference/commandlets/get-vaultfilebom:bomrowversiontype>) results in following issues:
  > - InvalidOperationException: *"Sequence contains more than one matching element"* for assemblies with enabled *multilevel* Structured-BOM containing updated sub-assembly with *copied components*
  > - [Bom_ItemQuantity](</code_reference/objects/filebomrow>) shows *1* for the components of a referenced *Phantom* assembly that got updated, and no new version of the main assembly is checked-in

## v19.0.3beta

`12-02-2018`

**General**

- Replaced Log4PostSharp with [PostSharp Diagnostics](<http://doc.postsharp.net/5.0/logging>) for extended Debug logging
- Re-enabled extended Debug [Logging](</logging>) for Vault 2019

**Fixed**

- Issue where logging did not work when powerVault was used in a 32-Bit process

## v19.0.2beta

`06-02-2018`

**Fixed**

- [Get-VaultFileBOM](</code_reference/commandlets/get-vaultfilebom>) with arguments *-GetChildrenBy* [LatestVersion](<code_reference/commandlets/get-vaultfilebom:bomrowversiontype>), [LatestReleasedVersion](<code_reference/commandlets/get-vaultfilebom:bomrowversiontype>) and [LatestReleasedVersionOfRevision](<code_reference/commandlets/get-vaultfilebom:bomrowversiontype>) results in one of following issues:

  > - *NullReferenceException*: *"Object reference not set to an instance of an object"* occurres when a referenced *Phantom* assembly and it's *merged* child component are updated, without updating the main assembly
  > - [Bom_PositionNumber](</code_reference/objects/filebomrow>) is *empty* for the component of a referenced *Phantom* assembly that got updated, and no new version of the main assembly is checked-in

## v19.0.1beta

`15-01-2018`

**Features**

- Added support for Vault 2019 (BETA)

:::{warning}
Extended Debug [Logging](</logging>) is disabled for Vault 2019
:::