I could go as far back as #Windows8, which this machine comes with, but setting up an older environment with the right version of #DotNetFramework, #DirectX, etc., is a challenge.
I could go as far back as #Windows8, which this machine comes with, but setting up an older environment with the right version of #DotNetFramework, #DirectX, etc., is a challenge.
via @dotnet : .NET and .NET Framework April 2025 servicing releases updates
https://ift.tt/WRnZhzB
#DotNet #DotNetFramework #April2025 #SecurityUpdates #CVE #ReleaseNotes #ASPNetCore #EntityFramework #SDK #Winforms #SoftwareDevelopment #Programming #DevCommunity…
via @dotnet : .NET and .NET Framework March 2025 servicing releases updates
https://ift.tt/rLuXd7N
#DotNet #DotNetFramework #March2025 #ServicingUpdates #SecurityImprovements #CVE #ReleaseNotes #ASPNetCore #EntityFramework #SoftwareUpdates #TechNews #DeveloperCo…
ASP.NET Core 2.3 Reships to Ensure Support for .NET Framework Users
In a strategic move to enhance support for ASP.NET Core users still on .NET Framework, Microsoft has reshipped ASP.NET Core 2.1 as ASP.NET Core 2.3. This update not only simplifies the upgrade process...
https://news.lavx.hu/article/asp-net-core-2-3-reships-to-ensure-support-for-net-framework-users
via @dotnet : ASP.NET Core on .NET Framework servicing release advisory: ASP.NET Core 2.3
https://ift.tt/EDKqgPM
#ASPNetCore #DotNetFramework #DotNetCore #Upgrade #NuGet #SoftwareDevelopment #WebDevelopment #TechAdvisory #Security…
via @dotnet : .NET and .NET Framework January 2025 servicing releases updates
https://ift.tt/eR6NaGf
#DotNet #DotNetFramework #January2025 #SecurityUpdates #CVE #RemoteCodeExecution #DenialOfService #ElevationOfPrivilege #ASPNetCore #EFCore #ReleaseNotes #Softwa…
I can understand why people would hate #entityframework after a few years working on an older #dotnetframework version. Updating the edmx and regenerating code is painful. It doesn't help that the tooling isn't great either. I spent 3 hours trying to get VS 2022 to correctly generate code and edmx changes from a database change. This should have taken minutes.
The newer #dotnet versions of EF Core are so much better.
.NET Framework Migration to .NET 9 by Derek Comartin.
https://codeopinion.com/net-framework-migration-to-net9/
#dotnet #dotnetframework #migration #upgradeassistant
.NET Framework Migration to .NET 9 by Derek Comartin.
https://codeopinion.com/net-framework-migration-to-net9/
#dotnet #dotnetframework #migration #upgradeassistant
.NET Framework Migration to .N...
Kudos to #Microsoft, that the #DotNetFramework migration to #DotNet is easier with #WPF than #WinForms (Why did you have to change all class names, inheritance hierarchies and stuff?)
@khalidabuhakmeh #Free #Rider who wants free licences from JetBrains #csharp #dotnet people #dotnet
#csharp
#aspnet
#dotnetcore
#dotnetdeveloper
#dotnetframework
#microsoft
#programming
#coding
#softwaredevelopment
see you there
Building a Plugin Architecture with Managed Extensibility Framework.
Incorporating extensibility features into a software system itself may not be inherently challenging. What proves more intricate is the discernment, assessment, or anticipation of when it is opportune and beneficial to introduce such extensibility points.
https://www.codeproject.com/Articles/5379448/Building-a-Plugin-Architecture-with-Managed-Extens
WinForms Designer Selection for 32-bit .NET Framework Projects.
#dotnet #winforms #csharp #visualstudio #windowsforms #windowsdev #dotnetframework
https://devblogs.microsoft.com/visualstudio/winforms-designer-selection-for-32-bit-net-framework-projects/
WinForms in a 64-Bit world – our strategy going forward by Klaus Loeffelmann.
#winforms #visualstudio #dotnet #windowsforms #windowsdev #64bit #dotnetframework #dotnetcore
https://devblogs.microsoft.com/dotnet/winforms-designer-64-bit-path-forward/
Microsoft migrated the real-time co-authoring service in the Microsoft Office suite of applications from .NET Framework 4.7.2 .NET 7.
Discover how they achieved: 30% CPU reduction
60% memory reduction
50% API latency reduction compared to the original service
Explore the details: https://bit.ly/3UxFg5G
Eso si, pensar que en las pruebas que he estado haciendo hoy, una aplicación cuyo EXE ocupa unos 500Kb (contiene algunos recursos gráficos y tal) pasa a:
1) Publicada como un único archivo (incluye todas las dependencias *.dll en el archivo) pero dependiente de que esté el #dotnetframework instalado. Ocupa 177Mb
2) Lo mismo pero incluyendo además todas las librerías del #dotntframework en el archivo. Ocupa 303Mb
Es un concepto chulo ya que puedes empaquetar dependencias y hasta las librerías del Framework utilizadas en un solo fichero ejecutable. De este modo la distribución es mucho más sencilla. Además, la aplicación lleva las librerías necesarias con lo que no es necesario tener la misma versión del #dotnetframework instalado
Holy moly!
647,000+ downloads of my #NuGet package which adds #owasp recommended security headers to #dotnet powered #aspDotNetCore applications.
I'm genuinely humbled.
https://www.nuget.org/packages/OwaspHeaders.Core
I'm also planning on doing a little work on it this week, live on stream.
I'll be taking support away for #dotNetFramework ahead of #dotnet8's release. But don't worry, version 7.5 (current latest) will still work with .NET Framework.
Are you a software developer still writing code for the original .NET Framework? Which version(s) are you using?
A recurring question that pops up at work is about the status of .NET Framework:
Has Microsoft discontinued it, or not?
The details are spread across multiple pages on the Microsoft website, so I have written a thorough summary, with links back to the relevant documentation.
https://dheinemann.com/posts/2023-03-24-is-dotnet-framework-discontinued
tl;dr: .NET Framework 4.8 is the final major release, but it will continue to be supported with security updates and bugfixes for the foreseeable future.