Compilation issues

[LexaGV]

I try to compile TW for .NET FW 4.8, almost everything is done, the last problems:

1. Incomplete class:

internal partial class SourceGenerationContext : JsonSerializerContext

Why it's needed at all to dig in JSON internals and make own JsonSerializerContext? And this SourceGenerationContext declared "partial", but there is no second part (implementation). Where it is? In sources there is nothing.

2. No any definitions for classes like INetFwPolicy2 - where they are?

I hope this project works as expected, but it looks overengineered. For plain Windows Defender Firewall wrapper it has too much code (just opinion).

[pylorak]

I try to compile TW for .NET FW 4.8, almost everything is done, the last problems:

1. Incomplete class:

internal partial class SourceGenerationContext : JsonSerializerContext

Why it's needed at all to dig in JSON internals and make own JsonSerializerContext? And this SourceGenerationContext declared "partial", but there is no second part (implementation). Where it is? In sources there is nothing.

It is specialized because the version that is used does not support (de-)serializing inheritance hierarchies, so a custom solution was necessary. Today, newer versions of the JSON source generator do support it out of the box, but there is no need to migrate over yet, and this way compatibility with old installations can be kept.
There is no digging in internals here. This is an officially supported technique, and I'm only using public API interfaces.

The "other part" of the partial class is not missing, it is supposed to be auto-generated during compile time by the compiler. You need to check your tooling why this doesn't happen.

2. No any definitions for classes like INetFwPolicy2 - where they are?

This is COM dependency and should be present on your computer. Again, the corresponding type import library should be auto-generated for the project on your computer. Similarly to the non-working source-generation above, this is a sign that dev tools are missing from or misconfigured on your computer. Are you using the supplied project file with Visual Studio? Also check that tlbimp.exe is installed (it should be on a default Visual Studio installation if the corresponding .Net Framework targets are selected).

I hope this project works as expected, but it looks overengineered. For plain Windows Defender Firewall wrapper it has too much code (just opinion).

It is NOT a wrapper for Windows Defender Firewall. That was only the case many years ago. Ever since 3.0, TinyWall interfaces directly with the kernel using the the user-mode API of the so called "Base Filtering Engine".