Posts

Showing posts from April, 2009

Wading through Jam

Ugh. It's a Friday afternoon and I have found myself wading through a serious amount of Jam. I have been working on an internal system of ours for some time (C# ASP.NET MVC). I have come across numerous problems with the latest development work I have been doing.

The problems I have come up against a numerous. For example I have 2 controllers that are related as they have the same ancestor class but they are slightly different. Now the easiest thing to have done is to have written 2 complete classes but the amount of duplication would be bad programming so I had to find out a way of getting round it. The way I have got round it is by creating a base controller class for them both and then using generics to get round the problem of the shared methods that were in the base controller.

As I almost finished the job I came to a realisation that on the view that I was developing, a user would could fill in information, then navigate away to add some data on another interelated view but wo…

Using Linq and generics with a Repository

Image
I have been creating a final year project piece for my part time study that I have called CabControl. Basically it is a piece of Taxi rank software. The design is made much easier as we only have to account for account work. I have tried to make the work I have done as close to commercially useable as possible however there are some obvious omissions and that is mainly because I have to do it in spare time in between a million other assignments and interests.

The course language is in VB.NET and the database we were advised to use was an Ms Access one. I could have done it like this and sure, it would have been easy but I really wanted to learn something out of this so I asked if I could use some more funky up to date technologies in mine and so have used C# .NET 3.5 and all that it includes.

One thing I really wanted use was the Linq to SQL classes. A lot of people have not taken to this in favour of NHibernate (including my work place) as the Linq to Sql has some questionable features…