This new version of f.lux has a grayscale mode and new key to turn it on: Windows + End.
The big surprise is how distracting the icons on the top and bottom of your screen are. These icon colors are the kind of thing you see in candy stores and on fire alarms, but we have to ignore them just to get work done. Without those colors, your computer looks more like a magazine that can help you focus on reading or thinking—it feels different, like a sheet of paper.
Source: What’s new with f.lux
In Visual Studio 2017 and with .NET Core projects a new way of referencing nuget packages was introduced. Somehow during a .NET project upgrade one of the nuget packages were converted into a PackageReference (referenced in the csproj file and not from package.config). Below are the steps to convert such package reference back into plain old package.config behaviour:
In addition to removing the PackageReferences from the project file, I also had to remove the following files from the $ProjectDir\obj directory: Myproject.csproj.nuget.cache Myproject.csproj.nuget.g.props Myproject.csproj.nuget.g.targets project.assets.json
Source: How can I revert to referencing Nuget packages in packages.config after using Package References in a .NET Standard project? – Stack Overflow
Common mistakes designers make and how to fix them
Source: Design Better Forms – UX Collective
When you reference a .js framework or library from your ASP.NET application, it makes sense to use the development version when you’re working on your own machine.
Referencing the development versions brings more useful error messages and integration with the React Developer tools.
But, you wouldn’t want to use these in production for performance reasons.
When you run the site in production, you’d want to reference the minified production versions of the React scripts.
Source: Different js scripts for different ASP.NET core environments· jonhilton.net – Making sense of .NET
Logging information in .NET, or really in any production application, is invaluable. In many cases, developers don’t have direct access to the production environment to debug issues. Good quality logs are the difference between solving problems like Sherlock Holmes and stumbling upon solutions like Inspector Jacques Clouseau. As you can imagine, we’re pretty big on logging here at Stackify, and we’ve written quite a few other blog posts on .NET logging frameworks. I’d encourage you to try out the search and read a few of our previous articles.
Source: NLog vs log4net vs Serilog: Compare .NET Logging Frameworks
Razor views are dynamically compiled by the ASP.NET runtime. If you want your views to be built at compile-time you could add the following option to your .csproj file:
You may take a look at the this article for more details.
Source: asp.net mvc – razor views are not giving compile time error – Stack Overflow
Set up SSH with Sourcetree on Windows
Source: Set up an SSH key – Atlassian Documentation
Are you annoyed by the default project location in Visual Studio? Check out this tutorial and learn how to modify it to suit you needs.
Source: Changing default project directory in Visual Studio 2017 – Daniel Zikmund