#net-framework — Public Fediverse posts

From the .NET blog...

In case you missed it earlier...

.NET and .NET Framework May 2026 servicing releases updates
https://devblogs.microsoft.com/dotnet/dotnet-and-dotnet-framework-may-2026-servicing-updates/ #dotnet #NETFramework #MaintenanceUpdates

From the .NET blog...

.NET and .NET Framework May 2026 servicing releases updates
https://devblogs.microsoft.com/dotnet/dotnet-and-dotnet-framework-may-2026-servicing-updates/ #dotnet #NETFramework #MaintenanceUpdates

From the .NET blog...

In case you missed it earlier...

VSTest is Removing its Newtonsoft.Json Dependency
https://devblogs.microsoft.com/dotnet/vs-test-is-removing-its-newtonsoft-json-dependency/ #dotnet #NETFramework #nuget #testing #visualstudio #vs #vstest

From the .NET blog...

VSTest is Removing its Newtonsoft.Json Dependency
https://devblogs.microsoft.com/dotnet/vs-test-is-removing-its-newtonsoft-json-dependency/ #dotnet #NETFramework #nuget #testing #visualstudio #vs #vstest

Removing byte[] allocations in .NET Framework using ReadOnlySpan<T> | by Andrew Lock

https://andrewlock.net/removingbyte-array-allocations-in-dotnet-framework-using-readonlyspan-t/

#dotnet #programming #csharp #netframework #memory #performance

via @dotnet : .NET and .NET Framework April 2026 servicing releases updates

https://ift.tt/wyUxFph
#DotNet #NET #NETCore #NETFramework #April2026 #ServicingUpdate #SecurityUpdate #CVE2026 #CVE2026-23666 #CVE2026-26171 #CVE2026-32178 #CVE2026-32203 #CVE2026-32226…

From the .NET blog...

In case you missed it earlier...

.NET and .NET Framework April 2026 servicing releases updates
https://devblogs.microsoft.com/dotnet/dotnet-and-dotnet-framework-april-2026-servicing-updates/ #dotnet #NETFramework #MaintenanceUpdates

From the .NET blog...

.NET and .NET Framework April 2026 servicing releases updates
https://devblogs.microsoft.com/dotnet/dotnet-and-dotnet-framework-april-2026-servicing-updates/ #dotnet #NETFramework #MaintenanceUpdates

via @dotnet : .NET and .NET Framework February 2026 servicing releases updates

https://ift.tt/VEgwPSb
#NET #DotNet #NETFramework #February2026 #SecurityUpdates #SecurityFixes #CVE21218 #ReleaseNotes #ASP.NETCore #EntityFrameworkCore #Runtime #SDK #Templating #WP…

.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.

via @dotnet : .NET Framework 3.5 Moves to Standalone Deployment in new versions of Windows

https://ift.tt/nmjbWrc
#NETFramework #NET35 #DotNet #Windows11 #InsiderPreview #StandaloneInstaller #LegacyApps #Migration #EndOfSupport #MicrosoftLearn #TechNews #Develop…

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

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:

• .NET Framework 4.6.2: January 12th, 2027
• .NET Framework 3.5 SP1: January 9th, 2029

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

Introducing ODP .NET 23.9: Enhanced Features for Distributed Transactions, AI, and More.

https://medium.com/oracledevs/introducing-odp-net-23-9-enhanced-features-for-distributed-transactions-ai-and-more-107ffdd497de

#oracle #dotnet #dataaccess #ai #database #odpnet #dotnetcore #netframework

Use Modern C# in .NET Framework Projects — Here's How! | with Mads Kristensen.

https://www.youtube.com/watch?v=dLAgn_vljqA

#csharp #visualstudio #dotnet #netframework

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:

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

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

via @dotnet : .NET and .NET Framework February 2025 servicing releases updates

https://ift.tt/S9TPOjh
#DotNet #NetFramework #DotNetUpdates #February2025 #DotNet9 #DotNet8 #ReleaseNotes #ASPNetCore #EFCore #WindowsForms #SoftwareDevelopment #TechUpdates #Programm…

Try out the .NET 10.0 Alpha SDK!

.NET 9.0 was released on November 12th, 2024, to provide your applications with brand new features, such as ref struct in interfaces, performance improvements, and bug fixes related to several of the .NET components.

Not so long after, .NET 10.0 alpha builds were spotted in the main installer GitHub repository, which is public. The table shows the platform table with two releases: .NET 9.0 and the upcoming .NET 10.0, which is going to be another LTS release.

The upcoming version of .NET will provide you with several of nice features, as well as performance improvements and bug fixes. This .NET version is to be released on November 2025 to accommodate with the release schedule, as well as its first preview to be scheduled for February 2025.

If you have Visual Studio 17.13 or later (may change across preview releases), you can now try out the Alpha builds of .NET 10.0, which you can find in the above link. Here are the links to .NET 10.0:

• Windows 64-bit (installer, zip)
• Windows 32-bit (installer, zip)
• Windows ARM64 (installer, zip)
• Linux 64-bit (deb, rpm, tar, musl tar)
• Linux ARM32 (tar, musl tar)
• Linux ARM64 (tar, musl tar)
• macOS 64-bit (installer, tar)
• macOS ARM64 (installer, tar)

Please note that this software is in its alpha state and may contain features that may not make it to the final release. Use with care.

Enjoy!

#Net #Net10 #Net100 #NETConsoleProject #NetCore #NetFramework #NetStandard #azure #C_ #dotnet #runtime #sdk #softwareDevelopment

New #blog post:

https://www.schafe-sind-bessere-rasenmaeher.de/tech/net-framework-and-code-coverage-from-the-terminal/

This week I managed to plug a hole in my terminal workflow that's been bugging me for a while.

It's related to #NetFramework, #CodeCoverage and my stubbornness for not wanting to use Visual Studio anymore. 😬

I count this as part of the #30DayFossChallenge , because all parts of the solution are FOSS.

I didn't really replace anything proprietary with this, but I plugged another hole that removing Visual Studio (Code) left. 🙂

Ich verzweifle gerade an UnitTests und dem alten .Net Framework 4.7.2. Manchmal habe ich das Gefühl, dass sich Objektorientierung und UnitTests ganz schön beißen können. Ich komme zumindest seit geraumer Zeit nicht sinnvoll weiter. Alte Frameworks sind halt auch einfach #LegacyCode 😤
#Programming #UnitTests #TTD #NetFramework #ObjektOrientierteProgrammierung

Using #SQLServer and the #NetFramework then you should install the November Update! #cve2022-41064