[News] MediaPortal 1 - 1.38 with x64 support released! (5 Viewers)

[catavolt]

Just encountered the same problem
MP won´t install because of the errors mentioned above (My Win version: Insiderbuild DEV v. 28000.1199)

 

[HSishi]

Visit the link in Post #28 ("Announcing Windows 11 ..."), download and install the complete Dot.Net framework 3.5 linked in that announcement.

 

[doskabouter]

Since 3.5 can't be installed within the mentioned Win11 and later versions, for now it's probably the best to provide the download link to the 3.5 installer while it's still working.
But that link won't work forever. It might be 3.5 or even 4.0 can't be installed in a future Windows version.

As for converting ... my (very basic) understandings are:

• The .net framework is a library of features you don't have to code by yourself in your apps because they're already ready-to-use and only need to be called with proper parameters.
• Newer versions of that library either still contain the features which have newer code for newer hardware / OS but have the same name, or the same features with newer names and calls which still do the same, so "only" editing the code at some places is required.
• But I also understand a large software like MediaPortal requires lots of checks if editings have to be made or not.

edit
The interesting bit is: One of the last updates of Windows removed 3.5. MediaPortal itself didn't notice or care and continued to run.
The problem occured when I tried to update from 1.36 to 1.38.

So maybe the solution is to simply check if 3.5 or even 4.0 is really required or already obsolete with newer versions and MP just needs any .net (framework) installed.

Well most of it is kinda true what you're saying but the transition from .NET Framework to .NET is substantial. As far as I remember there are quite a few things that are done in such a different way in .NET (like communicating with tvserver) that it is far from easy to make it work again on a more recent .NET version

 

[HSishi]

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 .NET Framework - Wikipedia .

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.

edit
Plus: Users aren't forced to install outdated software (.net framework 3.5) which might have security risks which don't get fixed anymore.