thecodegarden.net alternatives

sanushabalan.wordpress.com
Imagination + Action=Innovation


sanushabalan.wordpress.com site info

itq.eu
Innovative IT solutions for Hybrid Cloud, Cloud Native and Digital Workspace - ITQ
ITQ is a leading IT solutions provider specializing in Hybrid Cloud, Cloud Native and Digital Workspace. With a focus on tailored services, ITQ helps businesses optimize their IT infrastructure and drive innovation with a customer-centric approach.

itq.eu site info

handsonjones.com
Hands On Jones – Hands On: "Involving or offering active participation rather than theory"
Hands On Jones - Hands On: "Involving or offering active participation rather than theory"

handsonjones.com site info

mcguirev10.com
Forty Years of Code
A developer blog about C#, .NET, Azure, Unity games, and other topics

mcguirev10.com site info

ghousiaweb.wordpress.com
The Road to Success is under construction


ghousiaweb.wordpress.com site info

imgalib.wordpress.com
Galib's virtual identity - Shahriar Iqbal Chowdhury's Blog
Shahriar Iqbal Chowdhury's Blog

imgalib.wordpress.com site info

chrisstclair.co.uk
6 lesser-known features of C# / .NET that you should be using
Introduction This post is going to setup 6 features of the .NET Framework which I feel are under-utilised by a lot of developers - your opinion on whether they are under-utilised may differ from mine, but I hope some of you will find this post useful. 1. Stopwatch So I’m going to start with something we’ll use further on, the Stopwatch. It's quite likely that at some point, you'll have reason to want to profile parts of your code to find any performance bottlenecks. While there are a plethora of benchmarking packages you can use in your code (Benchmark.NET being one of the most popular), sometimes you just want to benchmark something quickly without any fuss. I imagine most people would do something like the below var start = DateTime.Now; Thread.Sleep(2000); //Code you want to profile here var end = DateTime.Now; var duration = (int)(end - start).TotalMilliseconds; Console.WriteLine($The operation took {duration} milliseconds); This works - it'll tell you it took ~2000 milliseconds. However, this is not the recommended way of benchmarking because DateTime.Now may not give you the required level of precision - DateTime.Now is usually accurate to roughly 15 milliseconds. To demonstrate this, see the very contrived example below: var sleeps = new List<int>() { 5, 10, 15, 20 }; foreach (var sleep in sleeps) { var start = DateTime.Now; Thread.Sleep(sleep); var end = DateTime.Now; var duration = (int)(end - start).TotalMilliseconds; Console.WriteLine(duration); } The output will likely change every time, but you'll likely get something like this: 15151531 So we've established it's not very precise, but what if you don't care? You can of course carry on using the DateTime.Now method of benchmarking, but there's a much nicer alternative called the Stopwatch which sits in the System.Diagnostics namespace. It's much neater than using DateTime.Now, and expresses your intent much more succinctly - and it's much more accurate! Let's change

chrisstclair.co.uk site info

esegece.com
Components Delphi, CBuilder, Lazarus and .NET
Delphi Components 100% full native code without external dependencies. Available for Rad Studio, Delphi, CBuilder, Lazarus and .NET. Create a single application and compile for the following personalities: Windows, MacOSX, Android, iOS and Linux.

esegece.com site info

dotnetplaybook.com
DotnetPlaybook - Your Ultimate Guide to .NET Development
Explore comprehensive tutorials, best practices, and resources for .NET development at DotnetPlaybook. Enhance your skills and stay updated with the latest in .NET technology.

dotnetplaybook.com site info

codetinkerer.com
codetinkerer.com | A blog about computers and coding, bouncing between professional software engineering practices and unabashed amateurism.
A blog about computers and coding, bouncing between professional software engineering practices and unabashed amateurism.

codetinkerer.com site info