Skip to content

Releases: Lombiq/Helpful-Libraries

v4.3.0

26 May 12:45
Compare
Choose a tag to compare

What's Changed

Full Changelog: v4.2.0...v4.3.0

v4.2.0

05 May 22:28
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v4.1.0...v4.2.0

v4.1.0

20 Apr 19:10
Compare
Choose a tag to compare

What's Changed

Full Changelog: v4.0.0...v4.1.0

v4.0.0

26 Mar 23:56
Compare
Choose a tag to compare

What's Changed

In this release, we've refactored Helpful Libraries into multiple projects, each specific to a given use-case, see the docs. This lets you use an appropriate Helpful Libraries project in your .NET and ASP.NET Core project even if you're not using Orchard Core (and this is what we also do in Hastlayer). This brings breaking changes but they're easy to fix in your project depending on Helpful Libraries:

  • Things were moved around, and Lombiq.HelpfulLibraries is now just a meta project referencing all other Helpful Libraries projects for easy reference. Thus, what you use might be in a different project and thus in a different namespace.
  • If you just want to make sure you get everything and don't care about excess dependencies, reference Lombiq.HelpfulLibraries. If you've referenced Lombiq.HelpfulLibraries before, then most possibly you get everything you need (in an Orchard Core app) from Lombiq.HelpfulLibraries.OrchardCore. Otherwise, use Lombiq.HelpfulLibraries.AspNetCore in a non-Orchard ASP.NET Core app, and Lombiq.HelpfulLibraries.Common in any .NET app (Lombiq.HelpfulLibraries.OrchardCore references both, and Lombiq.HelpfulLibraries.AspNetCore references Lombiq.HelpfulLibraries.Common).
  • The method signatures of Helpful Libraries features didn't change. So, apart from changing imported namespaces, you needn't adapt your code.

Full Changelog: v3.0.0...v4.0.0

v3.0.0

17 Mar 18:41
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v2.0.1...v3.0.0

v2.0.1

16 Feb 02:12
fd92284
Compare
Choose a tag to compare

What's Changed

  • OSOE-76: Removing unneeded Microsoft.VisualStudio.Threading reference that causes the analyzer to be applied in every consumer project by @Piedone in #120

Full Changelog: v2.0.0...v2.0.1

v2.0.0

15 Feb 21:01
8fbcfd8
Compare
Choose a tag to compare

First Orchard Core NuGet release.

1.9

07 Dec 18:33
Compare
Choose a tag to compare
1.9
  • Key Value Store for simple and efficient key-value pair storage
  • Moved Projector filters to Helpful Extensions
  • New extensions and utilities: HqlQueryExtensions, HqlExpressionFactoryExtensions and WebViewPageExtensions, UriHelper, MappingsManager
  • General code housekeeping and smaller improvements

1.8

07 Dec 18:31
Compare
Choose a tag to compare
1.8
  • JobManager and AtomicJobQueue
  • Making LockFile safer
  • MimeAssistant
  • Updating to VS 2012

1.7.1

07 Dec 18:31
Compare
Choose a tag to compare
  • Adding grouping to dynamic pages