home.social

#netframework — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #netframework, aggregated by home.social.

  1. .NET Framework 3.5 has become a standalone deployment

    .NET Framework 3.5 was released on November 19th, 2007, to include new features, such as LINQ, and was first available for Windows XP and Vista systems. It ran applications that were built for this framework version.

    When Windows 8 was released, it has been moved to an optional Windows component, which users can install on their systems whenever they require an application that supports this version of .NET Framework.

    Today, Microsoft has announced that .NET Framework 3.5 has been removed from the list of optional components, starting from Windows 11 Insider Preview Build 27965. This change doesn’t affect neither Windows 10 nor Windows 11 installations that are 25H2 or older.

    As a reminder, this version of .NET Framework will end its support on January 9th, 2029. You can read more about the announcement here.

    #NetFramework #NETFramework35 #dotnetfx #news #Tech #Technology #update
  2. Microsoft kann es auch: Änderungen am Code vornehmen und sich dann in den Urlaub (= "Ende des Supports") verabschieden, so dass neu eingebaute Fehler nicht mehr behoben werden.

    Der State in DrawListViewItemEventArgs enthält im DrawItem-Event seit Framework 4.8 immer das Selected-Flag. Auch wenn das Item gar nicht selected ist. Musste auf 4.7.2 zurückgehen damit der Fehler nicht mehr da ist.

    Murks.

    #Coding #Microsoft #NetFramework

  3. Ending support for .NET Framework for our projects on January 2030

    .NET Framework first made it to Windows systems on 2002 before being backported to Linux unofficially with the Mono project. Then, in 2016, everything changed when Microsoft had released .NET Core that aimed to be a cross-platform .NET framework to give developers the ability to create cross-platform applications. However, the legacy .NET Framework is still in use by enterprises and other workstations, because it would be costly to make a migration, especially when it comes to enterprise internal applications.

    Nitrocid had started as an application that was written with Visual Basic using the legacy .NET Framework 4.0 version, before moving to 4.8 before finally migrating to the modern .NET framework on 0.1.0, starting with .NET 8.0. During this period, we had created several libraries, including Terminaux, which all provided support for both the classic .NET Framework and the modern .NET.

    After that, we started testing everything under the modern .NET framework instead of what we’re originally aiming for, which makes the deprecation of our support of .NET Framework imminent.

    Today, we are announcing our decision to deprecate .NET Framework support for our projects, starting January 3rd, 2030.

    This deprecation was necessary to ensure that we move forward with our projects, because maintaining legacy support has become burdensome. However, not all projects will follow the same path, because we have libraries that are platform-agnostic, such as Nettify and Textify. Projects that use native libraries, such as BassBoom, and projects that reference them, such as Terminaux, will be affected by this decision.

    This list may change between now and January 9th, 2029, depending on how the development of our libraries goes, such as features that will be introduced in future versions. However, the release date has been finalized according to the factors, such as the following:

    On January 9th, 2029, we’ll start migrating libraries and their tests slowly to use only the modern .NET framework, and this migration will be done on the last week of each month until January 3rd, 2030.

    Photo by Darina Belonogova

    #Net #NetFramework #dotnetfx #microsoft #news #Tech #Technology #update #Windows

  4. .NET 10.0 LTS and Visual Studio 2026 released!

    The fifth Long Term Support (LTS) release for the modern .NET framework, .NET 10.0 has just been released! This release features performance improvements across various areas, feature additions, and many changes that will improve your .NET development experience.

    To download this version of .NET, visit the below link by clicking on the buttons shown below:

    Download Learn More Release Notes

    Not only that, but Visual Studio 2026 has become generally available to the public. Because of this, your development workflow will be improved tremendously due to the new features that it introduces, compared to Visual Studio 2022.

    To download Visual Studio 2026, visit the below link by clocking on the buttons shown below:

    Download Learn More

    Get yourselves excited with the .NET 10.0 release! Download .NET 10.0 by going to the top of the page and clicking on Download to get started!

    Visual Studio 18.0 will be shipped with built-in support for .NET 10.0 so that you can use this version of .NET with Visual Studio seamlessly.

    #Net #Net10 #Net100 #NETConsoleProject #NetFramework #NetStandard #csharp #VBNET #visualBasic #visualStudio #VisualStudio2026 #vs #VS2026

  5. Our NuGet total downloads reached 2M!

    We have finally reached 2 million downloads across all our NuGet packages, which consist of both the current and the past libraries that have been downloaded over the lifetime of our NuGet feed existence that started on August 2019. Thanks to everyone who have tried out our packages and used them in their applications!

    This is a minor milestone, but we are aiming for major ones, such as 5 million downloads across all packages. To celebrate this milestone, we’re introducing brand new versions of libraries. This is to add new features and to improve existing ones.

    Nitrocid 0.1.3 is going to have a major arrangement overhaul when it comes to the API, so we’re going to mark this by increasing the API version to v4.0 from v3.1 as it’s a huge breaking change. This will make sure that the Nitrocid application acts like a “launcher” for the core Nitrocid kernel, which, in turn, depends on the base kernel library. This is vaguely similar to how v0.0.20 was developed.

    Textify will be updated to improve the RTL reverse performance by getting rid of the libicu library in favor of the more efficient method after this experiment proves successful. As always, we are aiming to change how we make experiments to make sure that they don’t hinder the final production code, but, sometimes, we’d release a version that includes such experiments to gather feedback.

    We are going to try reducing the distribution size of Terminaux starting from v7.0, and Beta 3 will include this improvement to ensure that we reduce the download size, especially for future Nitrocid versions. We have already updated Terminaux 6.1.x to include this improvement, and docs have been already updated to reflect this change.

    Finally, we are going to introduce some subtle changes to the CI system across all projects, as well as some more build system improvements that we’ve promised, to improve build times and to increase reliability. This applies to developers only.

    Enjoy!

    #Net #Net6 #Net60 #NET7 #NET70 #Net8 #Net80 #Net9 #Net90 #NetCore #NetCore31 #NetFramework #NetStandard #C_ #csharp #NuGet #NuGetPackageManager #NuGetOrg #Package #PackageManager #Packages #Packaging #VBNET

  6. Mono is back! Mono 6.14.0 released!

    The first major version of Mono has been released after more than five years of no release. The WineHQ project has taken over the development of the .NET Framework version of Mono back on August 2024 after a fork has been made back in February 2024 under the project’s GitLab instance. This major version is under 6.14.0 and is available to download now.

    The release changelogs states that Mono finally has native support for macOS with ARM64 processors, which makes your developer experience when using such machines improved. In addition to that, there have been several improvements regarding System.Windows.Forms for Mono GUI applications to fix resource leaks, to re-implement clipboard and drag-and-drop functionalities, and to improve stability on X11.

    This release has also improved support for generated COM interfaces for apps that use them. Mono should no longer hang when the process is being exited in some common cases. In addition to that, Mono should no longer experience many bugs and many build warnings.

    For Gregorian users, Mono finally has support for the Gregorian language, which means that you can now use Mono in your native language to improve your user experience.

    To download Mono’s source code, click on the button below:

    Download source code

    https://audiomack.com/aptivi/song/mono-is-back-mono-6140-released

    #Net #NetFramework #C_ #csharp #dotnet #FrameworkMono #Mono #MonoRuntime #news #Tech #Technology #update