CortiWins

During the last days i created a workaround for us that solves it for us for now. Doing that made me realize that my previous description of net8 including the...

> This issue doesn't reproduce in separate NetFramework48 project or separate Net8 project, it only occurs when set multi target frameworks in a project `net8.0-windows;net48` From my tests, it is...

> [@CortiWins](https://github.com/CortiWins) - what happens when you change the .NET Framework project format to SDK style? Net SDK style created with 8.0, TargetFramework changed to 4.8 -> error Net Framework...

@SchoenGFM So, how did you solve it? I put all designer classes using the design time assemblies into their own project, so it's no longer linked when reflection accesses the...

@SchoenGFM We do not use MEF ( _what does that stand for? Microsoft Entity Framework, Managed Extensibility Framework?_ ). What we both do/did is apply reflection that leads to the...

@Zheng-Li01 Oh yeah, the type of the weakreference was changed. The risks of using reflection. This one if updated for that [DeadEventHandler_V2.zip](https://github.com/user-attachments/files/20725455/DeadEventHandler_V2.zip)

@merriemcgaw Yes. Versions i tested: - Classic Net Framework 48 - SDK Style Projects with targetframeworks net8.0-windows;net48 Btw. i "solved" it by forcing the static classes to create events from...