1.3.9

• Adds support for media entities to specify an automapped IMedia property containing the CMS entry similar to document types with IPublishedContent

1.3.5

Fixes issue with IPublishedContent not being mapped

1.3.4

Improvements:

• Not checking for case in entity names
• Checking Media and Entity Type Handler input for IPublishedContent before assuming string id

1.3.3

Bug Fix

• Updated MediaTypeHandler to return null when no media is found

1.3.2

Improvements to mapping process

• When mapping the current content to a model, updated to use the IPublishedContent from the PublishedContentRequest on the UmbracoContext rather than looking up the content by the assigned Id. This should be marginally more performant by avoiding doing an additional lookup, but also provides support for any libraries that provider virtual content that implements the IPublishedContent interface (i.e. Merchello)
• Updates the value transformation process to allows execute the type handler if one is present to ensure all transformations are done, even if value type and target type already match.

1.3.1

Bug Fixes

• Fixes issue where proxied models created from IContent models did not support recursive hydration.
• Fixes issue where if a proxy property was overwritten with some value not from CMS, it would not persist and would still use CMS value.
• Fixes issue where preview content breaks due to use of a singleton UmbracoHelper. [#34]

1.3.0

New Feature: Independence from Web Context

Extended the current UmbracoContext implementation to include a secondary implementation that removes any dependency on IPublishedContext, UmbracoHelper, and the Umbraco WebContext. Instead of using the WebContext as a vehicle for retrieving data from Umbraco, the ServiceContext is used. [#27]

Other

• Added PropertyInfo parameter to FillClassProperties to support additional behavior for libraries that extend Vault. [#25]

1.2.1

Fixes an issue where classes that used type inheritance would cause duplicate results to return in calls to GetUmbracoEntityAliasesFromType [#12]

1.2.0

New Feature: Lazy Loading (#6)

Umbraco Vault now includes support for lazy loading of properties. Properties that are expensive to hydrate,
such as collections, can be marked as virtual and they will be loaded when accessed. See article
for more detail on this feature.

New Type Handlers

• Vault now supports nullable types for primitives and structs. See https://github.com/thenerdery/UmbracoVault/wiki/Umbraco-Data-Type---C%23-Data-Type-Grid#nullable-data-types for more detail. (#15)
• Vault now supports mapping from JSON data stored within properties. See https://github.com/thenerdery/UmbracoVault/wiki/Umbraco-Data-Type---C%23-Data-Type-Grid#json-data for more detail. (#16)

Issues

• Fixed issue where exception would be thrown if loading an assembly threw an error. Added try/catch around logic and tracing any issues identified. (#11)
• Fixed issue if an external assembly attempts to register a type already handled, that an exception would be thrown. A trace warning is now written instead.

Other

• Codebase has been updated to build against VS 2015 and C# 6
• Reference sites for testing builds have been updated to the latest v6 and v7 versions, including ASP.Net MVC5
• Various internal accessiblity changes have been made to limit exposure of the API
• Various code cleanup

1.1.1

• The new base controller expected to be uesd with Umbraco has been renamed from VaultDefaultGenericController to VaultRenderMvcController in order to more closely
  Umbraco conventions
• VaultDefaultGenericController and VaultDefaultRenderController have been marked as obsolete.