Resume App Progress

I decided to forego the SCSF implementation of the Resume Builder after repeatedly getting assembly errors related to my references to Microsoft.Practices.CompositeUI library.

The advice was to delete the compiled dll files from the Debug / Bin folder. I did this a number of times and still get errors occassionally.

I deemed my SCSF installation unstable and went ahead to doing a plain old Windows form. I am currently in the process of incorporating NHibernate.

Initial challenges to installing NHibernate to my project involved getting errors related to configuration, in particular, Null Reference Exception. NHibernate has its own sequence of looking for the configuration file, and realized that I didn’t have to refer to the default configuration file explicitly. I merely had to ask the configuration object to add my current assembly, via AddAssembly, and moved my configuration settings from an external hibernate.cfg.xml file into app.config*. It worked.

*NHibernate has a number of ways to read configuration. You can set it programmatically by invoking methods directly, but this will reduce the maintainability of your app since you’ll need to recompile everytime settings need to be changed. You can add configuration entries into your app.config or web.config, or you can put the config in an external file, like hibernate.cfg.xml.

Having resolved that, I am now working on the mapping file. I have yet to fully familiarize myself with how it deals with one-to-many relationship collections, and other mapping concerns.

2 Comments

  1. just_curious said,

    May 9, 2008 at 12:40 am

    ever thought of trying out Castle ActiveRecord? it uses an attribute-based mapping on top of nhibernate.

  2. jasonbanico said,

    May 9, 2008 at 7:10 am

    Yes, I’ve been checking out ActiveRecord. I find appealing its use of attributes instead of the clunky mapping config file.

Post a Comment