It’s time to get serious about improving your programming skills. Let’s do it!
That’s an easy career improvement goal to give oneself, but “become a kick-$!! programmer” is not a simple goal. For one thing, saying, “I want to get better” assumes that you recognize what “better” looks like. Plus, too many people aim for improvement without any sense of how to get there.
Moq makes testing this piece of code a breeze. Without it, I would have had to write a whole lot of essentially throwaway code just to test this three line controller action. Probably one or two orders of magnitude more code. Clearly, this tool which I relied on heavily prior to .NET Core, remains quite a powerful weapon in my arsenal in .NET Core.
Prefix is a free profiler for ASP.NET applications. It's dead easy to use and it will help you find bugs in your code that you didn't even know you had. I found two in what I thought were properly working apps within an hour of downloading Prefix.
public static Task RunAndDispose(Func<Task> action)
{
try
{
action();
}
finally
{
System.Diagnostics.Trace.WriteLine("Finaly");
if (!HttpContextLifecycle.HasContext())
{
new HybridLifecycle().FindCache(null).DisposeAndClear();
}
}
return Task.FromResult(0);
} public override async Task RunAsync()
{
await SemaphoreSlim.WaitAsync();
try
{
if (this.IsShuttingDown || this.Pause)
return;
await IoCWrapper.RunAndDispose(async () =>
{
var draftsService = IoCWrapper.GetInstance<IBlogPostDraftsService>();
await draftsService.RunConvertDraftsToPostsJobAsync();
});
}
finally
{
SemaphoreSlim.Release();
}
} ActivatedEventTimeDurationThread
Activated Historical Code ContextException thrown: 'System.ObjectDisposedException' in mscorlib.dll ("The ObjectContext instance has been disposed and can no longer be used for operations that require a connection.") Exception thrown: 'System.ObjectDisposedException' in mscorlib.dll ("The ObjectContext instance has been disposed and can no longer be used for operations that require a connection.") Hyperlink: Activate Historical Debugging346.49s[14880] Worker Thread 
Among the over 100 API changes in .NET 6 are several features designed to make working with asynchronous code easier and safer. Here are some of the highlights.
On many of the expressions we’ve tried, these changes routinely result in throughput improvements of 3-6x, and in some cases, much more.
At Microsoft Build Live today, we are sharing a first look at our plans for .NET Core 3. The highlight of .NET Core 3 is support for Windows desktop applications, specifically Windows Forms, Windows Presentation Framework (WPF), and UWP XAML. You will be able to run new and existing Windows desktop applications on .NET Core and enjoy all the benefits that .NET Core has to offer.
To that end, the company has been building parts of the Android Open Source Project (AOSP) with Rust for the past 18 months, with plans in the pipeline to scale this initiative to cover more aspects of the operating system.
I have jotted down 10 of the best and must-have extensions for Chrome that will help you secure the browser and all your sensitive information
