We at Namics are pleased to announce a new stable release of NitroNet and NitroNet for Sitecore.
In the last 12 months we have gained more experience about how to work with NitroNet (for Sitecore) and our findings went straight into improvements for the two projects. And in the last weeks we did a great effort to test all these changes, to add some more important features and most importantly to extend, update and fix the documentation.
Different NuGets for all your Needs
The main focus with NitroNet for Sitecore was to make it compatible with specific Sitecore versions. This was done because of possible API changes that Sitecore applies with new versions. For example there were made crucial changes to the caching API in Sitecore 8.2. You can now find your suitable NuGet on the basis of the suffix. If you work with the latest version of Sitecore then pick the NuGet package with the highest suffix number.
So let’s say you want NitroNet.Sitecore with Unity support. Then there you have currently two options:
With every new Sitecore release that involves breaking changes there will be created specific NuGets for it. In addition a Microsoft DependencyInjection NuGet was added for Sitecore 8.2. It is the recommended NuGet to install if you are using Sitecore 8.2 because the installation process is very easy and Sitecore 8.2 already ships with Microsoft DependencyIncjection support.
If you want to read more about your installation options, click here.
It is now possible to configure which file extensions NitroNet should respect and to exclude specific file paths from the file watchers of NitroNet with the help of regex:
Now an example configuration is delivered with the NuGet too which you can take as a reference or basis for your own configuration. For further information about the config file click here.
Greatly improved Documentation
Most of the work which was done for this release went into the documentation. A huge effort was made to make working with NitroNet (for Sitecore) as easy as possible for you.
Also the focus of the documentation was shifted to working with a plain handlebars frontend. Because most of you will use a plain handlebars frontend and not Nitro which is extended handlebars. And despite the name, NitroNet is mainly a handlebars view engine and not only for use with a Nitro frontend. And if you want to work with your own customized handlebars frontend, it’s very easy to register your own handlebars helpers in NitroNet. The instructions were added here.
Thanks to the following persons which helped to make this release possible: