PS: Greetings from Bulgaria!

I have very stupid question. HOW and WHERE you will load all existing skills for an employee? The property skills is read only. I am wondering how you will do it.

Thanks so much for the informative screencasts. I learned a great deal from them.

I was running the units tests but saw an error:

failed: The container has not been initialized! Please call IoC.Initialize(container) before using it.
System.InvalidOperationException: The container has not been initialized! Please call IoC.Initialize(container) before using it.
at Rhino.Commons.IoC.get_Container()
at Rhino.Commons.IoC.Resolve[T]()
at Rhino.Commons.UnitOfWork.Start(IDbConnection connection, UnitOfWorkNestingOptions nestingOptions)
at Rhino.Commons.UnitOfWork.Start()

The error occurred in this line of all unit tests:

using (UnitOfWork.Start())

When I ran the portal web site, everything worked fine including the UnitOfWork.Start() in the web project. So, I guessed the problem was somewhere in the unit tests only. I was not sure why RhinoCommons was not getting the Castle container.

I google the error. Somebody mentioned that the versions of the Castle stack might not match. So, I pulled down NHibernate, Castle and RhinoCommons in the trunk and tried to build them using NAnt. But I ran into build error in NHibernate, researched for the error but had no luck so far.

Any ideas? Thanks.

What you are seeing in the screencasts where I quickly use a keystroke to re-order all the members of my class is a tool called ‘ClassCleaner’. I blogged about it (and the other tools that you see in the screencast) in a prior post here: http://unhandled-exceptions.com/blog/index.php/2008/07/16/confessions-of-a-developer-tool-hound/

If you are running a more recent build of DXCore/RefactorPro/CodeRush, the you will be interested in these two additonal posts here: http://unhandled-exceptions.com/blog/index.php/2008/11/28/cr_classcleaner-and-cr_documentor-builds-updated-for-dxcore-322/ and here: http://unhandled-exceptions.com/blog/index.php/2008/12/29/cr_classcleaner-build-updated-for-dxcore-323/ where I provide updated binary donwloads the add-in that are are compiled against the more recent and then the current DXCore release.

Note as mentioned in those posts, you don’t need the commercial coderush or refactorPro tools to run ClassCleaner, just the freeware DXCore run-time from Dev Express.

Glad you are enjoying the screencasts — thanks for the comments and hope this helps~!

Sorry for an additional question with can not be carried to Agile When I watched your screencasts I wondred, how quickly you work with code with Refactor Pro! and CodeRush. Please, could you tell a key combination which allows you to sort class properties with fields and put them to different regions? Or how to adjust CodeRush to achieve this goal? Thank you.

P.S. Thank you for screencasts, it’s very pleasant and exciting to watch how professional work with project Thank you one more time

Suppose we were to add “tagging” capabilities to both Skill and Employee. What would be the best way to implement it? If Skill and Employee implements ITaggable, how would this look like in DDD? More interestingly, how would the persistence look it?

Thanks,
kebin

Logging will be coming in the app, I promise. Just later on as we layer more functionality into the system.

Thanks for the input~!

I have been following your current series and like it. IMHO, I think you probably might be missing on logging functionality. If this is something you can consider, it would be a great asset to this series.

Thanks,
-Bharani

If you are (for whatever reason) unable to use NHibernate (or any other mature, non-MS full-fledged ORM tool) then your only real choices are going to be either LINQ2SQL or (gasp!) Entity Framework. Even with the troubles that both of these technologies have when compared to just about any other mature ORM product (OSS or commercial) out there today, either LINQ2SQL or EF will get you further faster than trying to ‘roll-your-own’ ORM or just using ‘raw’ ADO.NET directly.

But both LINQ2SQL and EF have their challenges (technological and political/organizational).

LINQ2SQL is rumored to be near its end-of-lifecycle as a MS technology (e.g., much as with WinForms vs WPF, WinForms isn’t going away any time soon but neither will it get any more attention/features and the same now seems to be true of LINQ2SQL) and so basing a new app on what is essentially a sundowning technology seems a poor long-term decision.

EF has its own challenges, not the least of which are all of the technology issues (that I won’t bother to rehash here as you can find them for yourself all over the rest of the Internet) but also because there is a complete lack of non-MS-database-providers for EF at this time. Oracle, for example, had been rumored to be working on a provider for EF but has (my best info) postponed its release for an indeterminate amount of time b/c their own performance testing of the thing leads them to believe that releasing a provider for EF for Oracle will actually HURT them in the marketplace (a completely defensible marketing position and one that doens’t bode well for EF adoption since one of the points of EF was DB-agnosticism but EF as it exists today is a pure-MS play — and only SQL 2005/2008 at that, no Access, no XML data source, etc.).

I think that if you are interested in trying to be ‘agile’ and focus on some of the core principles that I (and others) espouse and you are ’stuck’ with only the universe of MS-provided solutions then you are probably best off looking at some of the refactoring efforts for Oxite presently being undertaken by someone like Rob Conery who is attempting to steer that project away from the brink of disaster but within the limits of a MS-centric data-access technology ( http://blog.wekeroad.com/blog/oxite-refactor-take-1/ )

There exists right now a very real (unanswered) question in my mind as to whether the MS-only universe of provided software infrastructure libraries is actually capable of being the (exclusive) foundation atop which one could build a solution that remains true to some of the ALT.NET / Agile / SOLID / DDD fundamentals. Hopefully with what Rob is undertaking, we will soon see some of the answer to this question.

I’m watching to see myself, frankly.