Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Try using a factory pattern.</p> <pre><code>using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.Reflection; namespace SO { class Program { static void Main(string[] args) { MessageFactory factory = new MessageFactory(); IMessage msg = factory.CreateObject(1); IMessage msg2 = factory.CreateObject(2); } } public interface IMessage { short Message_ID { get; } } public class Generic_Message1 : IMessage { public short Message_ID { get { return ID; } } internal const short ID = 1; } public class center_message1 : IMessage { public short Message_ID { get { return ID; } } internal const short ID = 2; } public class MessageFactory { private Dictionary&lt;short, Type&gt; messageMap = new Dictionary&lt;short, Type&gt;(); public MessageFactory() { Type[] messageTypes = Assembly.GetAssembly(typeof(IMessage)).GetTypes(); foreach (Type messageType in messageTypes) { if (!typeof(IMessage).IsAssignableFrom(messageType) || messageType == typeof(IMessage)) { // messageType is not derived from IMessage continue; } IMessage message = (IMessage)Activator.CreateInstance(messageType); messageMap.Add(message.Message_ID, messageType); } } public IMessage CreateObject(short Message_ID, params object[] args) { return (IMessage)Activator.CreateInstance(messageMap[Message_ID], args); } } } </code></pre> <p><strong>EDIT to answer comment:</strong></p> <p>If the "generic" library is the one processing the messages, and it has no knowledge of the types of message is is processing, you obviously have to change that.</p> <p>Either move to a "plug-in" model where your custom message dlls will be loaded from a specific directory on startup of the generic library, or read the custom message dlls from a config file at startup for the generic library.</p> <pre><code>// Read customMessageDllName and customMessageClassName from your config file Assembly assembly = Assembly.Load(customMessageDllName); IMessage customMessage = (IMessage)assembly.CreateInstance(customMessageClassName); </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POProblem with Order of "Registration" of .NET Classes in a Messaging Scenario
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USGalacticJello
    1. USGalacticJello
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COThis doesn't address the problem. I have the factory under control. The problem is putting these in two separate libraries, Generic not knowing about Center. Thanks for the suggestion.
      singulars
      1. PO
      1. USLimited Atonement
    2. COActually, it directly addresses your problem. As long as the IMessage implementations exist in the Application Domain, they will be instantiated without you having to call an Init on them.
      singulars
      1. PO
      1. USGalacticJello
    3. COMy first assessment was too quick. Your answer is better than I thought (upvote). I can't quite get it to work, though. The type IMessage is defined in the 'generic' assembly, the executing assembly when this needs to take place is the 'generic' assembly, the entry assembly is the program that gets and sends messages, the calling assembly is the 'generic' assembly. In short, I don't have a reference to the 'center' assembly. Any suggestions?
      singulars
      1. PO
      1. USLimited Atonement
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload