• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Upgrade of .NET version of tools

arno

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,240
Country
netherlands
As I already mentioned in this blog post from the end of last year, I am going to upgrade the .NET version that the tool use. Currently the tool use .NET Framework 4.8, but while developing I notice that a lot of third party library are nowadays only available for more recent .NET version. For example the latest version of the Assimp library that is used to read various 3D formats (like COLLADA, FBX) is not available as an easy package for the .NET version I use now. And also when working on the mesh optimization compression of glTF file I noticed that libraries to support this compression are only available for recent .NET versions.

Therefore I have decided that I will upgrade my tools to the current long term support (LTS) version of .NET. At the moment .NET 8.0 is the LTS version. Every two years Microsoft releases a new LTS version, so my intend is to keep track with that. That means every two years the tool will update the .NET version they use to the current LTS version.

I do realize that this change does affect certain users, as has been discussed on the forum already. .NET 8.0 is only available for Windows 10 and Windows 11. So this means that users still running older Windows versions will have to use the older (stable) releases that still target the older .NET version. But given that Microsoft is no longer supporting these old OS versions (even Windows 10 will be end of life later this year), I think the right decision is to switch to an actively supported .NET version now.

The last two weeks I have been working on the migration to .NET 8.0 already and I have all applications and the unit tests running in the new version now. I need to do some more testing to ensure that the functionality is working correctly, but I hope to release the update in a week or two from now. I will post another announcement when the release is imminent, but I wanted to inform all of you now already about the upcoming change.

Continue reading...
 
You must log in or register to reply here.
Back
Top