.NET

1857 readers
1 users here now

Getting started

Useful resources

IDEs and code editors

Tools

Rules

Related communities

Wikipedia pages

founded 3 years ago
MODERATORS
126
127
128
129
130
131
132
133
 
 

The VS extension

GitHub Copilot app modernization - Upgrade for .NET is a public preview AI-powered experience that helps you bring your .NET applications to the latest version quicker and more confidently than ever before. Powered by GitHub Copilot and Agent Mode, it serves as an intelligent upgrade companion that understands your code, determines the right upgrade path, and applies changes step-by-step with minimal manual effort.

This public preview focuses on Core-to-Core upgrades, such as: .NET Core 3.x, 5, 6, or 7 → .NET 8 or .NET 9

If your solution is currently on .NET Framework (e.g., .NET Framework 4.8):

  • Use the existing .NET Upgrade Assistant to upgrade from .NET Framework to .NET Core (.NET versions 3.x, 5, 6, etc.).
  • Once on .NET Core, you can use GitHub Copilot app modernization - upgrade for .NET for the rest of the upgrade process.
134
135
136
137
138
139
140
141
142
143
144
 
 

In this blog post, I will dive into how .NET 9.0 machine code for AVX-512 is sub-optimal and what changes were made to speed up Sep for AVX-512 by circumventing this, showing interesting code and assembly along the way, so get ready for SIMD C# code, x64 SIMD assembly and tons of benchmark numbers.


Sep - GitHub

World's Fastest .NET CSV Parser. Modern, minimal, fast, zero allocation, reading and writing of separated values (csv, tsv etc.). Cross-platform, trimmable and AOT/NativeAOT compatible.

145
146
 
 

cross-posted from: https://lemmy.world/post/29344357

I'm wondering if anyone here has gone through this process, and what the experience was like. (I'm not asking for help with any particular error or anything like that. At least not yet).

I got put in charge of maintaining an old codebase that includes Xamarin projects for android and ios and we seem to have run into a situation where we need to update the framework not just for security, but to keep the mobile app fully functional as Apple and Google update their APIs.

I did see that there was a button in Visual Studio to automatically upgrade the project, but apparently "upgrade" means "break fuckin' everything" so I'm guessing I'll need to take a more manual approcach and also blow a bunch of hours on finding replacements for all the dependencies that required Xamarin and are no longer maintained.

My biggest problem is that I haven't even heard of Xamarin before this thing got dropped in my lap so I have some confusion about how it's supposed to work on top of my normal baseline amount of confusion.

147
148
149
150
view more: ‹ prev next ›