How dikotl/paal2-lab3 works
Project type and purpose
• This is a multi-language laboratory project (Lab3) demonstrating dynamic array operations in C#, F# and VB.NET.
• It consists of:
• Three language-specific class libraries (ClassLibraryCS, ClassLibraryFS, ClassLibraryVB) implementing array operations.
• A Main console application (Main) that ties everything together via a CLI.
• A Tasks library (Tasks) containing assignment tasks or sample data.
• A Tests project exercising the C# implementation.
• The README confirms it’s purely algorithmic/educational, not a client-server or UI-rich system.
File structure
• Top-level solution file Lab3.sln orchestrates all projects.
• ClassLibraryCS/FS/VB each contain their own project file and implementation subfolders.
• Main holds the CLI entry point (CliArgs.fs, Main.fsproj, TaskSelectorMenu.fs).
• Tasks is a small C# project with task definitions.
• Tests is an MSTest project targeting only ClassLibraryCS.
• .github/workflows/main.yml for CI build & test.
• README.md documents the lab assignment.
README for additional insights
• Blocks 1 & 2 describe requirements for one-dimensional and jagged arrays.
a. Main components
• CLI Application (Main)
• C# Class Library (ClassLibraryCS)
• F# Class Library (ClassLibraryFS)
• VB.NET Class Library (ClassLibraryVB)
• Tasks Library (Tasks)
• Tests Project (Tests)
• External: .NET SDK & Command-Line Environment, GitHub Actions CI
b. Relationships & interactions
• Main → references → ClassLibraryCS, ClassLibraryFS, ClassLibraryVB, Tasks
• Tasks → defines input data or problem statements consumed by Main and libraries
• Tests → references → ClassLibraryCS (validates array operations)
• GitHub Actions → triggers build+test on Lab3.sln
c. Architectural patterns & principles
• Separation of concerns: each language has its own library, Main is language-agnostic CLI.
• Modular design: Tasks are decoupled from implementation details.
• Test-driven: MSTest project validates core C# library.
• CI pipeline ensures cross-language build integrity.
d. Key technologies/frameworks
• .NET Core/SDK, F# scripting
• MSTest testing framework
• GitHub Actions for CI
• CLI argument parsing in F#
Detailed capture of essential elements
• Break out each ClassLibrary’s submodules (e.g., Collections, FunctionalOperations in CS) if deep detail is desired.
• Tasks as a shared resource invoked by Main and potentially by tests.
• If documenting I/O variants, group “Console / File / Random generator” as a subcomponent of Main or the libraries that handle input.
Putting it all together:
• Left side: User → CLI (Main: CliArgs, TaskSelectorMenu)
• Center: 3 parallel libraries (CS, FS, VB) each with their own namespaces/folders
• Right: Tasks library feeding input/data models
• Bottom: Tests project targeting ClassLibraryCS
• Top: GitHub Actions (build & test) on Lab3.sln