PLEASE FOLLOW THESE INSTRUCTIONS – thanks 🙂

1 – Select the Download link below or Download the ZIP file from here

2 – If you get the prompt: “Zip is Not Commonly Download” please use Pull Down selection: “Keep” – It is Safe

3 – Locate the zip in your download folder and move to a new folder named “MessagingSystem” or a name of your choice

4 – Expand the ZIP into the newly created folder

5 – Use the Database Backup File to create the SQL 2008 Database Data Model – If it can’t be installed in your dB version, the documentation on this page can be used to create it from scratch: It is a Simple Model and all default data is detailed on this page

6 – Select the solution file: MessagingSystem.sln and open in VS2012

7 – Validate the Entity Framework App config connection string is correct for your Database

8 – Compile the solution

9 – Run the Test Runner to validate functionality of all of the components

If you have ReSharper, its test runner will appear when you open the solution. If you don’t have ReSharper you can download a free 30 day trial version. I strongly recommend doing so. 

If not, the VS2102 test runner will work: Cnt +T,R,A 0r Menu – Test- Run – All Tests

The VS 2012 Solution Code for Enterprise Messaging System Demonstration

1. The Component Entity
   1. ComponentName – String
      1. Name of the Solution Assembly
      2. Primary Key of the Component Lookup Table
      3. Used as Part of the Compound Primary Key in the ComponentMessage Data Entity
   2. Description – String
      1. Information about the Component
      2. Primary use is for a Web Application for Management of the Messaging System to Display the Component Details
   3. Default Entry – “MessagingSystem”
2. ComponentMessage Entity
   1. MessageTag – String
      1. Part of the Compound Primary Key
         1. MessageTag
         2. ComponentName
      2. Unique Identifier for Messages within an Assembly Component
         1. A String Value within the Entity
         2. Referenced from assembly ENUMs
            1. ENUM creates an Intellisense List for Dynamic Reference of available messages during development
            2. Converted to a String for processing within the DataOps Data Layer
         3. Enables Global Messages within an Assembly
         4. Message Reuse Such as “No Records Found” Message
      3. Defaults
         1. “None” – Unit Test for Bad Parameter Sad Test
         2. “InactiveRecord” – Unit Test for IsActive Flag false Sad Test
         3. “NoRecordsFound” – Global Message
   2. ComponentName – String
      1. Part of the Compound Primary Key
         1. ComponentName
         2. MessageTag
      2. Foreign Key Unique Identifier for the Component Lookup Table
         1. Identifies the Assembly Component Name
         2. Creates a Collection for Filtering with the MessageTag
      3. Default Entry – “MessagingSystem”
   3. MessageTag – String
      1. Foreign Key Unique Identifier for the MessageType Lookup Table
         1. Identifies the Message Category Type
         2. Used for Categorization of the Messages into Types
      2. Default Entries
         1. “Information”
         2. “Error”
   4. Message – String
      1. Actual Text Message
         1. Referenced by
            1. MessageTag
            2. ComponentName
         2. Text this is used within the Error Handling Pattern
      2. Field for Updating Message to comply with Open/Closed Principle
      3. Default Entry – “No Records Found in the Messaging System Request”
   5. IsActive – Boolean
      1. A Flag for Current Message Availability
      2. Defaults to true
      3. Set to false to prevent Message from being displayed
      4. An Error Message of “No Message Found” with be Returned if Flag is false
3. MessageType Entity
   1. Message Types – String
      1. Name of the Message Type
      2. Primary Key of the MessageType Lookup Table
      3. Default
         1. Information
         2. Error
   2. Description – String
      1. Information about the MessageType
      2. Primary use is for a Web Application for Management of the Messaging System to Display the Message Type Details

A Complex Composite DTO that passes the Compound Key values to the Messaging System to retrieve the requested Message using a string version of the Enum Message identifier: MessageTag.

A DTO that is available for any Solution-centric common data they may be required in the Message Request.

The default flag is a “Success” Boolean.

Creates an Intellisense list of registered Messages that are available to the Error Handling Design Pattern.

The Enum list selection is converted to a String Type and passed as a Parameter to the Messaging System via the MessageInfoRequest DTO.

A DTO that contains the Message information for a Single Message.

A Behavior Method Class that creates all the Messages for the ComponentMessageEntity Class.

All messages are created using a Static Constructor from the Entity Framework Data Context and made available to the consuming Class.

A DTO that contains the All Message information in the entire System.

This could be used for a Messing Caching System solution.

All Messages are created upon instantiation of the type.