This is probably a silly question, but as I moved into the "custom" portion of my application (i.e., the code that I'm writing that will use the framework from Vince's book), I began to wonder if there were any pitfalls to breaking out the framework code into their own libraries, so different applications could use the same framework.

In other words, V2.DAL.Framework could become something like V2.Framework.DAL (and the BLL would be V2.Framework.BLL). Say you had two applications, HRPaidTimeOff and HRTravelExpenses - both applications could use the same DAL and BLL libraries, without having to include the code in both applications.

Anyone see any potential or obvious downsides to that?

I haven't given much thought about what to do with the UI layer...maybe make it web application for the framework portion? Of course, you might need a different look and feel for the two applications.

Tim