Blog about software development
NHibernate still rocks! Even with quite a bit old code base it is still at the top of the c# frameworks we daily use. Especially the framework extensiblity is tremendous. Now I am going to show you how we use NHibernate in the multitenant fashion.
With recent jsreport announcements of visual studio reporting extension and .net embedded reporting it should be pretty easy to generate pdf reports from any c# application. I decided to take a shot and extend official asp.net MVC 5 Contoso University example with reporting capabilities using jsreport.
NHibernate has very powerful syntax for doing sql queries. It's QueryOver syntax is the biggest reason for using NHibernate instead of Entity Framework for me.
One of the session/transaction handling technique in NHibernate is called session/transaction per request. The name of this technique is self explanatory.
In the last post it was explained how to prepare unit test hierarchy for writing tests interacting with database. In this post I will concentrate
I remember the first time I saw the using statement in c#. It was actually used when reading file content.
Quite some time ago I blogged about rendering pdf reports in c#. Recently we have added excel reports into jsreport and it was released with a little delay also into .NET. This means you should be able to use both html-to-xlsx and xlsx recipes to create excel files from your .NET environments now.
Such a very common thing like adding an existing external volume to Amazon elastic beanstalk is not easily supported out of the box. The official blog mentions only how to attach a snapshot or how to attach and overwrite a new volume every time the service starts. It took me a while to make the config file actually adding an existing volume without formatting it every time so I share it here with you...
The best practice when adding email notifications feature to your system is to separate as much as you can from email body assembling to email sending outside of the core system. The emails templates quite likely often changes and you don't want to deploy the system because of every single notification change. The best is to just separate everything into an external system and give the access to your PR or Marketing department so they change emails as the time goes without affecting the core system.
Hi! My name is Jan Blaha. I'm software developer and startup enthusiastic. See my current work.
janblaha.net