I use vbnet with dotnet. I want to build a function WriteMessages that takes a List(of…
- User
I use vbnet with dotnet.
I want to build a function
WriteMessagesthat takes aList(of ParsedMessages)and should write them. I want to modularize the function so that I can write to one or multiple files or even send the data somewhere else. So I do NOT want to hardcode one strategy, e.g. write to file. How can I make this function open for change and e.g. adhere to the Single Responsibility Principle? - Assistant
You're on the right track by thinking about not hardcoding one output strategy—it’s a classic case for applying the Strategy Pattern or Dependency Injection, adhering to SOLID principles, especially:
- S: Single Responsibility Principle (SRP)
- O: Open-Closed Principle (OCP)
- D: Dependency Inversion Principle (DIP)
✅ Goal:
You want a modular
WriteMessagesfunction in VB.NET that can write to file, network, database, or any destination, without changing the core function each time.
🎯 How to Achieve This
We'll define a
IMessageWriterinterface with a method likeWrite(messages As List(Of ParsedMessage)).Then, you can implement different strategies:
FileMessageWriterNetworkMessageWriterConsoleMessageWriter, etc.
💡 Step-by-step Implementation
1. Define the ParsedMessage Class
Public Class ParsedMessage Public Property Id As Integer Public Property Content As String ' Add other properties as needed End Class
2. Define the Interface
Public Interface IMessageWriter Sub Write(messages As List(Of ParsedMessage)) End Interface
3. Concrete Implementations
File Writer
Public Class FileMessageWriter Implements IMessageWriter Private ReadOnly _filePath As String Public Sub New(filePath As String) _filePath = filePath End Sub Public Sub Write(messages As List(Of ParsedMessage)) Implements IMessageWriter.Write Using writer As New StreamWriter(_filePath, append:=True) For Each message In messages writer.WriteLine($"[{message.Id}] {message.Content}") Next End Using End Sub End ClassConsole Writer (Alternative target)
Public Class ConsoleMessageWriter Implements IMessageWriter Public Sub Write(messages As List(Of ParsedMessage)) Implements IMessageWriter.Write For Each message In messages Console.WriteLine($"[{message.Id}] {message.Content}") Next End Sub End ClassMultiple Writers at Once
If you want to write to multiple destinations:
Public Class CompositeMessageWriter Implements IMessageWriter Private ReadOnly _writers As List(Of IMessageWriter) Public Sub New(writers As IEnumerable(Of IMessageWriter)) _writers = writers.ToList() End Sub Public Sub Write(messages As List(Of ParsedMessage)) Implements IMessageWriter.Write For Each writer In _writers writer.Write(messages) Next End Sub End Class
4. The WriteMessages Function
Inject the writer:
Public Sub WriteMessages(messages As List(Of ParsedMessage), writer As IMessageWriter) writer.Write(messages) End Sub
✅ Example Usage:
Dim messages As New List(Of ParsedMessage) From { New ParsedMessage With {.Id = 1, .Content = "Hello"}, New ParsedMessage With {.Id = 2, .Content = "World"} } Dim fileWriter As New FileMessageWriter("messages.txt") Dim consoleWriter As New ConsoleMessageWriter() Dim combinedWriter As New CompositeMessageWriter({fileWriter, consoleWriter}) WriteMessages(messages, combinedWriter)
👓 Benefits Achieved:
- SRP:
WriteMessagesnow has a single responsibility — to delegate the writing. - OCP: Add new writers (e.g., Database, MQTT) without modifying
WriteMessages. - DIP: Writers are passed in —
WriteMessagesdepends on an abstraction.
🧠 Optional Enhancements
- Use
Asyncif writing is I/O-heavy. - Use a DI container if you’re building a larger app (like using Microsoft.Extensions.DependencyInjection).
- Add logging and error handling for more robustness.
Would you like me to help write unit tests for this setup?
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.