When comparing .NET Core and .NET Framework, it is essential to consider various factors such as performance, cross-platform support, deployment options, and future-proofing. Here’s a detailed comparison between the two to help you decide which is best for your needs: 1. Performance .NET Core: Generally faster and more efficient than .NET Framework. Microsoft has made significant performance improvements in .NET Core, especially in areas like server-side web applications and microservices. Kestrel, the web server in .NET Core, is highly optimized for performance, especially in handling asynchronous operations and modern hardware architectures. Garbage Collection (GC) and JIT (Just-In-Time) compilation have been improved in .NET Core to reduce latency and improve throughput. Supports tiered compilation, which optimizes hot paths of code over time for better performance. .NET Framework: Performance is generally good for most traditional desktop and enterprise applications. However, it lacks many of the modern performance optimizations found in .NET Core. The web server in .NET Framework, IIS, is more mature but not as optimized for high-performance scenarios, especially compared to Kestrel in .NET Core. Verdict: .NET Core offers better performance, especially for web applications, cloud-based services, and applications that require scalability. 2. Cross-Platform Support .NET Core: Cross-platform, meaning it can run on Windows, Linux, and macOS. If you are building applications that need to be deployed across multiple operating systems, .NET Core is the clear choice. .NET Framework: Only runs on Windows. It is tightly integrated with the Windows operating system and is not portable across other platforms. Verdict: If you need cross-platform support, .NET Core is the way to go. 3. Application Types .NET Core: Ideal for building web applications (ASP.NET Core), microservices, cloud-native apps, console apps, cross-platform libraries, and high-performance APIs. It supports modern development practices like Docker containers, Kubernetes, and serverless architectures. Does not fully support desktop applications like Windows Forms or WPF (though .NET Core 3.1 and .NET 5+ added partial support). .NET Framework: Best suited for Windows-specific applications, especially legacy desktop applications built with WPF or Windows Forms. If you are working with older enterprise applications that require compatibility with Windows-only technologies like COM, WCF, or Windows Services, .NET Framewor

We'll know soon. /ravi My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com

dandy72 wrote: Which doesn't make them valueless. But you said "...books were just taking up place in a number of boxes on the floor of a closet." You wanted the storage. You didn't want to build an addition onto your house to provide that storage. Which is the same problem the library has. Except multiplied by thousands.

I initially was going that route, but I ran into issues with ILMerge with certain projects. It's been so long now I couldn't tell you what the issue was, but CSBrick was built because ILMerge didn't work in all cases. Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix

To implement sending WhatsApp OTP for TOTP (Time-based One-Time Password) in ASP.NET using LINQ operations, you'll need to: 1. Generate TOTP: Use a library that supports TOTP generation. 2. Send the OTP to WhatsApp: You can use services like Twilio, Vonage, or WhatsApp Business API to send messages via WhatsApp. 3. Verify the OTP: Store and verify the TOTP against the user input.

I have a friend that can't retire at 70 because she's a 35yr RPG expert. Makes over $300/hr. fixing critical issues and has a backlog of waiting clients.

Can I replace the egg with a sausage? :-D "I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!

I despise K&R bracing. I have ALWAYS used Allman (for the last 45 years), and at work, we're using K&R (apparently the go-to bracing used in javashit). I hate it. It's unnatural. Curious note: I never knew the bracing styles had names. I always referred to them as "the way I do it", and "not the way I do it". ".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013

Nelson1965 wrote: I would like the windows I open not to appear in the Task Manager The dream of malware authors everywhere! No, you can't hide your application from the task manager. At least not without writing and installing a "rootkit", which will get your application banned with extreme prejudice. Nelson1965 wrote: when I log out to turn off the computer it tells me that there are open windows You don't need to hide your application from the task manager to avoid that. Any normal application will shut down when the user logs out. If you need to do something special when that happens, subscribe to the Application.SessionEnding event[^]. "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

raddevus wrote: If you don't have the deconstructor in your class and you try the destructuring you will get an error Unless you have a deconstructor extension method, which can be handy for third-party classes that don't provide them: // In your "SimpleShapes.dll" assembly: public class Rectangle(float width, float height) { public readonly float Width = width, Height = height; } // In my application code: public static class Shapes { public static void Deconstruct (this Rectangle rectangle, out float width, out float height) => (width, height) = (rectangle.Width, rectangle.Height); } "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

Ah! Makes sense. Thanks! The difficult we do right away... ...the impossible takes slightly longer.