Reply to thread

Message

<blockquote data-quote="HSishi" data-source="post: 1304369" data-attributes="member: 167861">The transition from one type of library to another is a big change, agree.But .net framework is embedded in Windows since Windows Vista and gets maintained by Windows Update.See <a href="https://en.wikipedia.org/wiki/.NET_Framework" target="_blank">.NET Framework - Wikipedia</a> .As I said, on my PC MediaPortal 1.36 ran fine even after .net framework 3.5 got removed with Win11 Insider Canary #27965 so all functionality seemed to be provided by 4.8.1.In my humble opinion, the MP installer could simply skip the .net framework check because if the requirements for MP are met (Windows Vista and newer), a .net framework is present and, assuming Windows Update isn't suppressed, up-to-date.editPlus: Users aren't forced to install outdated software (.net framework 3.5) which might have security risks which don't get fixed anymore.</blockquote>

[QUOTE="HSishi, post: 1304369, member: 167861"] The transition from one type of library to another is a big change, agree. But [B].net framework[/B] is embedded in Windows since Windows Vista and gets maintained by Windows Update. See [URL='https://en.wikipedia.org/wiki/.NET_Framework'].NET Framework - Wikipedia[/URL] . As I said, on my PC MediaPortal 1.36 ran fine even after .net framework [B]3.5[/B] got removed with Win11 Insider Canary #27965 so all functionality seemed to be provided by 4.8.1. In my humble opinion, the MP [B]installer [/B]could simply skip the .net framework check because if the requirements for MP are met (Windows Vista and newer), a .net framework is present and, assuming Windows Update isn't suppressed, up-to-date. [I]edit[/I] Plus: Users aren't forced to install outdated software (.net framework 3.5) which might have security risks which don't get fixed anymore. [/QUOTE]

Verification