Monthly Archives: November 2014

MicroLite Extension Release Candidates

A release candidate for all the MicroLite extensions has been released built against MicroLite 6.0-rc. As with the MicroLite 6.0-rc, these are still to be considered pre-release so don’t roll them into production just yet!

When the final build of each extension is released along side MicroLite 6.0, I will publish full release notes and an upgrade guide but here’s a couple of pointers if you want to try out the release candidates:

Mvc and WebApi extension

The .NET 4.5 build of both the extensions now use the Async version of the Session API added in MicroLite 6.0, if you use the .NET 4.5 build you will need to use IAsyncSession instead of ISession and IAsyncReadOnlySession instead of IReadOnlySession.

WebApi extension

The method signature for the MicroLiteApiController<T> and the MicroLiteODataApiController<T> helpers has changed from:

protected virtual HttpResponseMessage ...

to

protected virtual Task<HttpResponseMessage> ...

So for the Get method you would need to update from:

public HttpResponseMessage Get(int id)
{
    return this.GetEntityResponse(id);
}

to

public Task<HttpResponseMessage> Get(int id)
{
    return this.GetEntityResponse(id);
}

DbEncryptedString

The DbEncryptedString class has now moved to a new package MicroLite.Extensions.Cryptography.

MicroLite 6.0 RC

The release candidate for MicroLite 6.0.0 has been released on NuGet, please feel free to download it and try it out.

This contains fixes for 3 bugs I found in beta 2 whilst running some integration tests with each of the supported database servers.

The RC build will be re-released as the final 6.0.0 build unless any further defects are uncovered, I expect to publish the final release some time before the end of November 2014.

If you find any bugs, please raise them in the GitHub Issues along with any necessary information to reproduce it (or better yet, a pull request with a failing unit test) and we’ll make sure it’s squashed before the final release.

MicroLite 6.0 Beta 2

A second beta for MicroLite 6.0.0 has been released on NuGet, please feel free to download it and try it out.

This contains a fix for a bug I found in the previous beta whilst updating some of the extensions to work with the new async methods.

There are some breaking changes in MicroLite 6.0 which make them incompatible with some functionality in the current versions of the Mvc extension (5.3.0) and WebApi extension (4.3.0). The extensions will be updated alongside MicroLite 6.0 when the final build is released but at this point in time, there are no beta builds for the extensions.

Remember, this is a beta so use it for testing only, not production code!

If you find any bugs, please raise them in the GitHub Issues along with any necessary information to reproduce it (or better yet, a pull request with a failing unit test) and we’ll make sure it’s squashed before the final release.

MicroLite 6.0 Beta

A beta for MicroLite 6.0.0 has been released on NuGet, please feel free to download it and try it out.

We will cover the changes in a series of blog posts, but here are the main things to be aware of:

  • Support for async/await in the session API in the .NET 4.5 build
  • Attribute mapping has moved namespace to MicroLite.Mapping.Attributes
  • DbEncryptedString has been moved into its own MicroLite.Extensions.Cryptography project and package – this will be published along side the final MicroLite 6.0 build
  • Support for specifying the DbType of a property
  • Support for dynamic connection strings (in addition to named connection strings)
  • Updates to the Delete and Update SqlBuilders to make them more on par with the Select builder
  • Improved logging and debugging support
  • Removed methods marked as obsolete in MicroLite 5.0-5.3

Unfortunately, we have not had time to finish the Oracle and Sybase implementations so they won’t be included in 6.0, they will have to wait for MicroLite 6.1.

Remember, this is a beta so use it for testing only, not production code!

If you find any bugs, please raise them in the GitHub Issues along with any necessary information to reproduce it (or better yet, a pull request with a failing unit test) and we’ll make sure it’s squashed before the final release.