Algojammer is an experimental, proof-of-concept code editor for writing algorithms in Python. It was mainly written to assist with solving the kind of algorithm problems that feature in competitions like Google Code Jam, Topcoder and HackerRank

• Fixed an issue that caused Xamarin.Android projects using the Xamarin.Android.Arch.Work.Runtime NuGet package to fail with "class file for com.google.common.util.concurrent.ListenableFuture not found".
• Fixed Link assemblies causes app crashes if you have an EditText in VS2019 Preview 2
• Fixed error 'Some or all identity references could not be translated' when opening extension manager; fixed failure to persist some IDE settings.
• Fixed Parallel Stacks shows nonsense number of threads
• Fixed After repair, build cmake folder fails with D8050, compile using tasks.vs.json fails with "cl" is not recognized
• Fixed No longer able to group by trait in Test Explorer with VS 2019 Preview
• Fixed Some c++ code analysis warnings are not localized
• Fixed Service Fabric Project not loading
• Now correctly reports $(MSBuildVersion) as 16.2.x, instead of the erroneous 16.200.19.
• Fixed issue causing a random crash after closing GoToAll/Symbol UI.
• Fixed crash during Visual Studio sign-in.
• Fixed an issue where forms previewer on Android frequently stops responding and needs a restart.
• Added iOS Designer Xcode 10.3 support. 

This post provides a simple IValueConverter implementation that makes use of the framework type converters in order to convert between a large range of source / target types. This converter can be used both within bindings and in code-behind to give more concise property setters. 

When developing controllers in ASP.NET Core, there are certain practices that should be avoided to ensure maintainability, performance, and adherence to best practices. Here are 12 things we should avoid in our controllers. 

I spent some time reviewing GitLab features and determined that, by our Buyer-Based Open Core model, eighteen features that appear in seven different stages of the DevOps lifecycle ought to be open source

This bug-fix update resolves the following issues:

ReSharper Build couldn’t build a project if MSBuild was installed as part of Visual Studio 2019 Preview 1 (RSRP-472694).
Visual Studio froze on JavaScript debugging (RSRP-472802).
Inconsistent default state around ‘Inconsistent Naming‘ inspection (RSRP-472812).
A false positive for NUnit TestCase (RSRP-472787).
Unit test coverage highlighting is not shown for projects targeting .NET Framework 3.5 and lower (DCVR-9525).
False “Cannot convert type” error for Promise in TypeScript.
Find Usages did not process bodies of #define macros when looking for textual occurrences (RSCPP-24977).
“Remove unused parameter” quick-fix was broken in C++ (RSCPP-25094).
 

In Defense of Lazy Loading

I don’t know how this happened but for the last couple years (at least), whenever I read an author who writes about ORMs, I often see a sentiment like this: “ORMs are fine, just make sure you disable this pesky feature called Lazy Loading”.

It’s like this feature is not even needed and only brings confusion and performance issues to everyone who chooses to use it. Well, as you may guess from the title of this article, I disagree with this point of view completely. 

Microsoft today released the first stable version of Microsoft Edge. Build 79.0.309.65 can be downloaded from Microsoft's official web site. 

It has only been about a year since .NET Core 1.0 RC came out. We are now getting close to .NET Core 2.0. We have been playing with .NET Core since the betas and feel like the quality of the 1.0 runtime was very good. Our only complaint has really been odd Visual Studio behavior. We would expect that with 2.0, the adoption of .NET Core is likely to skyrocket.