Development

The feedback was very good, and I was glad that everybody liked it. Jordev is really moving ahead, and I am very excited being part of it 🙂 Below is the slide show (it’s an enhanced version from my previous one): Introduction To NHibernate (SlideShare) Code is the same of the previous one which you can download from here

I wanted to map an integer enumeration type in NHibernate, I googled “mapping enumeration in NHibernate” and the best explanation was of Jeremy Miller in his post here. But as it appears (and according to my understanding) that the enumeration type should be mapped to a database column of characters type (varchar, char,…etc). What if the database column was int? well…do exactly like what jeremy did except simply use “NHibernate.Type.PersistentEnumType” instead of “NHibernate.Type.EnumStringType“. ...

Do you go through the same, time-consuming, frustrating discussion with your colleagues when you want to decide what to have for lunch? well…this is exactly what we have been going through where I work. To solve the problem (partially, because humans can never totally agree! ), I made a small, quick and dirty web application; LunchPoll. The user (Active Directory user, it works on Windows Authentication) would go to the home page, select the available poll: ...

From the very first day I have heard about Agile development and I have been hearing things like “code comments are not such a good thing” The main idea behind that is that the code should be self explanatory; giving functions good names and splitting concerns into different functions. But what about the “why”; why this certain code is written this way? why not do it that way? and this is what I have gone through today! ...

I have delivered the presentation I talked about in my previous post here. Actually it was pretty simple and straightforward, the slides them selves don’t have code content; all the code was shown in VS directly (I always found it better to see the code in its really environment to better understand). The attendees were handful, but if felt really great when they expressed how excited they were about the whole thing. ...

The other day I wanted to create an HQL query to retrieve data from one object (WorkOrderFault) that has many-to-many relation with another. so I created the following: ISession session = NHibernateOrmSessionFactory.CurrentNHibernateSession; IQuery query = session.CreateQuery( "select wof from WorkOrderFault wof join wof.WorkOrderTechnicians as tech where tech.Id = 43334"); IList<WorkOrderFault> objects = query.List<WorkOrderFault>(); The query ran successfully, and I got my results. Then I wanted to use paging and get certain amount of results starting from certain record, so I added these two lines directly after I instantiated the IQuery object: ...

In one of the modules I am working on, my unit tests used to take tremendous amount of time (4 minutes per test 🤢. I inherited the NHibernate config file from previous NHibernate test module that was used somewhere before! At the beginning I thought that this is something common when you use NHibernate with rich applications, so I didn’t pay much attention, but then it became a real headache. ...

Ok, now I am facing a hard decision; what to do next in my technical life? In order to reach for better decision, I drew a mind map using this wonderful online tool Mindomo, it’s like the following: Those nodes are the things I think I want to study/do most. I marked the most important ones with the red, yellow and then blue flags. Then marked the ones I need to do most urgently with 1 being the most urgent, 2 less urgent and so on. ...

In my company, we are working on this big GRP project, lots of pages, projects and workflows, soon we are delivering some modules to the customer. So today, while trying to test a workflow that we have been working for days, something weird happened; the users of the workflow didn’t exist anymore!! After searching for a while, it appeared that we are delivering some modules, and real data needed to be deployed on a database especially for deployment, basically the Users table was the primary table! so as simple as it gets…they created the new database and changed the users we used for the real users (along with the hierarchical structure of the employees). Ok…that’s fine for now, but the problem is that they wanted us to work on the new data; the action was that they changed the users on the development database on our development environment! ...