Put an “N” in front of it, or add “.NET” to the back. Part III

See Part I and Part II for previous projects. 

I hadn’t added this one because some time ago they used IKVM to use it on .NET. But I’ve just went back to the site and saw they are working on a real .NET port, so here it is: 

Oops, looks like I was a bit to fast here, the IKVM is included in the project so it’s probably not a real port. Well, I’ll just leave it here.


The Practical Traveller

The holidays are back again, and everyone is preparing for their holiday trip. Our European roads are stuffed with cars filled with people and their luggage. They all share a common goal:

“Get there co-travellers as fast and comfortable possible to their destination”

There are of course different ways for drivers to prepare for the trip.
Continue reading

NHibernate Part 3: Mapping techniques for aggregation – One To One mapping

Updated code available for NHibernate 2.0.1.GA here.
The toolingset used is Visual Studio 2008 and Sql Server 2008

I finally got to writing my next post on NHibernate. I will be discussing Aggregation. I’m not an expert on NHibernate mapping but have done some experimentation in preparation for a project I’m working on and this post reflects my experiences during this experiments. If you should find any errors or know of other best practices, please let me know so that I can correct them.

But first, let me introduce to you the basic application that we will continue to use in the rest of this series.

Continue reading

Monitoring Visual Sourcesafe

Everybody knows Visual SourceSafe just sucks. But still a lot of people are using it. So are we.

We experienced following recently (it’s really the basic “stepping on each-others toes” scenario):

  • Someone (Person1) did a “Get Latest” and got the most recent code on his machine.
  • Another developer (Person2) also did a “Get Latest” and got the most recent code on his machine.
  • Now, Person2 checks out the code and starts editing it, and when finished checks in his changes.
  • Then Person1 starts making changes after checking out the code. However, because he didn’t do another “Get Latest”, he doesn’t have the most recent code. When he now checks his changes back in, the changes from Person2 are lost.

I then went searching for a tool to monitor SourceSafe for certain events like checking in files. On “The Code Project” I found the following tool:

SSMonitor – Monitor a Visual SourceSafe database using VBScript

After installing it as a service on each developer machine and configuring it for monitoring “Check-In” we get an e-mail when someone checks-in his changes. Great tool! Thanks Doug. Thanks Codeproject.