Sometimes I want to use the enterprise library, but just not all 200+ MB of the thing.  So I go about piecing together the pieces I want, by project, into the main solution.  This can be troublesome as all the pieces don’t just drop in simply.

First Bump in the Road :: GlobalAssemblyInfo.cs

The first problem I’ve run into this time around was the GlobalAssemblyInfo.cs file wasn’t available.  After fiddling around a minute I realized this needed to be added to the solution at a global level.  The way to do this is to right click and add existing file to the actual Solution.  Unfortunately I had statically added a copy of this file to my projects I was adding and simply re-added those projects with the appropriate file mapping again.  Note to self, “If adding individual blocks from the enterprise library make sure to add the GlobalAssemblyInfo.cs file first and then the individual blocks”.

Second Bump ::  The “Common” Project

The common project is used in pretty much every single project in the enterprise library solution.  For some reason when I added all my projects, the common reference went away in numerous projects.  So this was a case of just adding the reference back to several of the projects.  Maybe I shouldn’t add them this way, but regardless, it gets the job done.

So far I’m now up and running, but just wanted to present a searchable note about these bumps I’ve hit.  Once these things are resolved the library blocks are flawless.

Yesterday was rough going, mainly just because there was so many topics to cover.  Today I hope to nail a ton more functional code segments, requirements, and get some unit tests in my work.

Yesterday

• Finished clarification of the task list and working to find the priorities for this iteration.
• Met to clarify design goals and functional requirements for new features.

Today

• Core focus will be on functional requirements and getting the respective unit tests, preferably via TDD for the interface based controller and presenter code.  I’ll be happy with test after for the UI elements since they’re all COM Interop.  i.e.,  today is code day.

Tomorrow

• Continue focus on functional specifications and respective tests.

Road Blocks & Risks

• Continued – Time constraints have all but eliminated efforts to research or implement a proof around the PIAB, limiting our exception handling, logging, and other cross cutting concerns we need to have in place.
• Continued – The IoC and DI architecture points have not been clarified.  The more UI work we do without these pieces in place the more tightly coupled, untested, and unworkable refactor efforts will be in the future.
• Continued – Significant risks include; lack of significant code coverage from unit tests, unclear way for testing the upper layers of Excel/UI functionality.

So yeah, if you don’t know him, or haven’t worked with him, or haven’t tasted any of his fine beverages you should make a point to meet this guy.  If you can…

I’m fortunate I got to work with Mr. Thatcher as he is an A+ Developer (That’s an A+ without a bell curve either, if that was the case he’d have like a 180% and I don’t know what that letter would be – maybe AAA+ or something)

Anyway, he’s gettin famous so read up about the fella.

We scrummed, but then kind of fell of into planning today.  Thus no real serious throughput was achieved.  We did rectify many questions and clarify what was meant for many of the specifications for the application.  It was a very productive day, just not in code productivity.

Yesterday

1. Finished clarification of the task list and working to find the priorities for this iteration.- Met to clarify design goals and functional requirements for new features.

Today

1. Finish clarification of the iteration priorities.  Break items down to more specific functional goals.- Met with others on other functional topics to provide consult on my functional task topics.- Started some code clean up, minor change requests, and another refactor effort against some of the existing UI Views.

Tomorrow

1. Begin research of the PIAB (Policy Injection Application Block).- Figure out where and how our IoC (Inversion of Control) and DI (Dependency Inversion) architecture points will meet.- Implement the beginnings of a vertical integration with these concepts.

Road Blocks & Risks

1. Time constraints have all but eliminated efforts to research or implement a proof around the PIAB, limiting our exception handling, logging, and other cross cutting concerns we need to have in place.- The IoC and DI architecture points have not been clarified.  The more UI work we do without these pieces in place the more tightly coupled, untested, and unworkable refactor efforts will be in the future.- Significant risks include; lack of significant code coverage from unit tests, unclear way for testing the upper layers of Excel/UI functionality.

I’m not sure if this would be interesting or not to others, but first and foremost this blog is about me maintaining a history of what I do on the projects I work, what I’m accomplishing, and the technologies I’m working with.  With that said this is entry Part #1 of numerous entries I am going to attempt to start writing based on daily efforts and the stand ups that I attend.

Yesterday

1. Finished view find functionality.  This included the UI, presenter, and test data for the functionality.
2. Finished the add multiple single items, add single items multiple times, and their associated UI and presenter code.

Today

1. Begin refactor of yesterdays code, clarification and refactor of previously written code.
2. Start another set of unit and integration tests for the next phase of functionality.  Make sure I have coverage, as far as feasible, for the existing functionality.
3. Meet and discuss functionality for near future revisions, additions, and changes.

Tomorrow

1. Begin research of the PIAB (Policy Injection Application Block).
2. Figure out where and how our IoC (Inversion of Control) and DI (Dependency Inversion) architecture points will meet.
3. Implement the beginnings of a vertical integration with these concepts.

Road Blocks & Risks

1. No significant road blocks at this time.
2. Significant risks include; lack of significant code coverage from unit tests, unclear way for testing the upper layers of Excel/UI functionality.