Skip to content

Upgrade project to .NET 6 and add GitHub Actions workflow#1

Merged
CodeMangler merged 1 commit intomasterfrom
feat/upgrade-dotnet6-github-actions
Jun 5, 2025
Merged

Upgrade project to .NET 6 and add GitHub Actions workflow#1
CodeMangler merged 1 commit intomasterfrom
feat/upgrade-dotnet6-github-actions

Conversation

@CodeMangler
Copy link
Copy Markdown
Owner

This commit brings several major updates to the EventLogAnalyzer project:

  1. Framework Upgrade:

    • All projects (Console Client, EventLog, UnitTests) have been upgraded from .NET Framework 2.0 to .NET 6.
    • Project files (.csproj) have been converted to the modern SDK-style format.
    • The NUnit testing framework reference in UnitTests has been updated to use NuGet packages (NUnit 3.13.3, NUnit3TestAdapter 4.5.0, Microsoft.NET.Test.Sdk 17.3.2).
  2. Build System:

    • The primary build mechanism is now dotnet build using the EventLogAnalyzer.sln solution file.
    • Obsolete build scripts (build.bat, eventloganalyzer.build) have been removed.
    • The System.Diagnostics.EventLog NuGet package (v6.0.0) was added to EventLog.csproj to resolve compatibility issues with EventLogEntryType.
    • Fixed build issues related to duplicate EmbeddedResources and assembly attributes in Console Client.csproj.
  3. GitHub Actions CI:

    • A new GitHub Actions workflow (.github/workflows/dotnet-build.yml) has been added.
    • This workflow builds and tests the solution on windows-latest (due to Windows-specific EventLog APIs) for pushes and pull requests to the main branch.
  4. Codebase Cleanup:

    • Removed obsolete solution files (EventLog Analyzer - VS 2005.sln, EventLog Analyzer - VS 2008.sln).
    • Removed the local lib/nunit.framework.dll.
    • Removed EventLog/EventLog.idc.
    • Removed the Output/ directory (build artifacts) from source control and added it to .gitignore.
    • Added .vs/ to .gitignore.
    • Deleted AssemblyInfo.cs files as their content is now managed by the SDK-style projects.
  5. Documentation:

    • README.md has been updated with new build instructions for .NET 6.

This commit brings several major updates to the EventLogAnalyzer project:

1.  **Framework Upgrade:**
    *   All projects (Console Client, EventLog, UnitTests) have been upgraded from .NET Framework 2.0 to .NET 6.
    *   Project files (.csproj) have been converted to the modern SDK-style format.
    *   The NUnit testing framework reference in UnitTests has been updated to use NuGet packages (NUnit 3.13.3, NUnit3TestAdapter 4.5.0, Microsoft.NET.Test.Sdk 17.3.2).

2.  **Build System:**
    *   The primary build mechanism is now `dotnet build` using the `EventLogAnalyzer.sln` solution file.
    *   Obsolete build scripts (`build.bat`, `eventloganalyzer.build`) have been removed.
    *   The `System.Diagnostics.EventLog` NuGet package (v6.0.0) was added to `EventLog.csproj` to resolve compatibility issues with `EventLogEntryType`.
    *   Fixed build issues related to duplicate EmbeddedResources and assembly attributes in `Console Client.csproj`.

3.  **GitHub Actions CI:**
    *   A new GitHub Actions workflow (`.github/workflows/dotnet-build.yml`) has been added.
    *   This workflow builds and tests the solution on `windows-latest` (due to Windows-specific EventLog APIs) for pushes and pull requests to the `main` branch.

4.  **Codebase Cleanup:**
    *   Removed obsolete solution files (`EventLog Analyzer - VS 2005.sln`, `EventLog Analyzer - VS 2008.sln`).
    *   Removed the local `lib/nunit.framework.dll`.
    *   Removed `EventLog/EventLog.idc`.
    *   Removed the `Output/` directory (build artifacts) from source control and added it to `.gitignore`.
    *   Added `.vs/` to `.gitignore`.
    *   Deleted `AssemblyInfo.cs` files as their content is now managed by the SDK-style projects.

5.  **Documentation:**
    *   `README.md` has been updated with new build instructions for .NET 6.
@CodeMangler CodeMangler merged commit 27e413e into master Jun 5, 2025
@CodeMangler CodeMangler deleted the feat/upgrade-dotnet6-github-actions branch June 5, 2025 07:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant