#dotnetfx — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #dotnetfx, aggregated by home.social.
-
.NET Framework 3.5 no longer becomes a Windows optional component, starting from Windows 11 build 27965.
#dotnet #dotnetfx #csharp #programming #Windows #Microsoft #TechNews #TechUpdates
-
.NET Framework 3.5 no longer becomes a Windows optional component, starting from Windows 11 build 27965.
#dotnet #dotnetfx #csharp #programming #Windows #Microsoft #TechNews #TechUpdates
-
.NET Framework 3.5 no longer becomes a Windows optional component, starting from Windows 11 build 27965.
#dotnet #dotnetfx #csharp #programming #Windows #Microsoft #TechNews #TechUpdates
-
.NET Framework 3.5 no longer becomes a Windows optional component, starting from Windows 11 build 27965.
#dotnet #dotnetfx #csharp #programming #Windows #Microsoft #TechNews #TechUpdates
-
.NET Framework 3.5 no longer becomes a Windows optional component, starting from Windows 11 build 27965.
#dotnet #dotnetfx #csharp #programming #Windows #Microsoft #TechNews #TechUpdates
-
.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 -
.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 -
.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 -
.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 -
.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 -
Support for .NET Framework for our libraries will end on January 3rd, 2030.
#dotnetfx #csharp #programming #TechNews #TechUpdates #dotnet #library #libraries #Windows #Microsoft #MicrosoftWindows
-
Support for .NET Framework for our libraries will end on January 3rd, 2030.
#dotnetfx #csharp #programming #TechNews #TechUpdates #dotnet #library #libraries #Windows #Microsoft #MicrosoftWindows
-
Support for .NET Framework for our libraries will end on January 3rd, 2030.
#dotnetfx #csharp #programming #TechNews #TechUpdates #dotnet #library #libraries #Windows #Microsoft #MicrosoftWindows
-
Support for .NET Framework for our libraries will end on January 3rd, 2030.
#dotnetfx #csharp #programming #TechNews #TechUpdates #dotnet #library #libraries #Windows #Microsoft #MicrosoftWindows
-
Support for .NET Framework for our libraries will end on January 3rd, 2030.
#dotnetfx #csharp #programming #TechNews #TechUpdates #dotnet #library #libraries #Windows #Microsoft #MicrosoftWindows
-
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.
#Net #NetFramework #dotnetfx #microsoft #news #Tech #Technology #update #Windows
-
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.
#Net #NetFramework #dotnetfx #microsoft #news #Tech #Technology #update #Windows -
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.
#Net #NetFramework #dotnetfx #microsoft #news #Tech #Technology #update #Windows -
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.
#Net #NetFramework #dotnetfx #microsoft #news #Tech #Technology #update #Windows
-
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.
#Net #NetFramework #dotnetfx #microsoft #news #Tech #Technology #update #Windows
-
GRILO is going soon…
GRILO is a C# application that allows you to simulate the bootloader of a computer. It’s customizable because it provides an interface that can let you make any application bootable, and it can be found in a separate package called GRILO.Boot. However, we have plans regarding this application, and it’s going to be good and bad news.
Nitrocid KS 0.1.1 will include its own bootloader implemented using the GRILO code but modified to work more closely with Nitrocid KS. This means that we have to archive GRILO as a standalone application.
Nitrocid KS 0.1.1 will feature a bootloader similar to how modern versions of Windows work; the bootloader screen will show up after the system integrity verification. This is to allow mods to implement their own bootable application.
The code structure is going to be the same. This means that Nitrocid.Boot will be implemented as a package that features the same code as GRILO.Boot.
We’re sad to announce that GRILO as a standalone app will no longer be in development after Nitrocid KS 0.1.1 is released. There will be no more GRILO versions, but the Nitrocid version will continue to be improved, ensuring that it works more closely with Nitrocid KS.
Enjoy!
#Net #Net6 #Net60 #NET7 #NET70 #Net8 #Net80 #Net9 #Net90 #NETConsoleProject #NetCore #NetCore31 #NetFramework #NetStandard #abandoned #application #ApplicationUpdate #bootManager #bootloader #csharp #dotnet #dotnetfx #EndOfLife #EOL #grilo #OutOfSupport
