Velocity.js animation engine

velocityjs.org/
Velocity.js Overview
Velocity is an animation engine with the same API as jQuery’s $.animate(). It works with and without jQuery. It’s incredibly fast, and it features color animation, transforms, loops, easings, SVG support, and scrolling. It is the best of jQuery and CSS transitions combined. Download
Download Velocity, include it on your page, and replace all instances of jQuery’s $.animate() with $.velocity(). You will immediately see a performance boost across all browsers and devices — especially on mobile. Compatibility
Velocity works everywhere — back to IE8 and Android 2.3. Under the hood, it mimics jQuery’s $.queue(), and thus interoperates seamlessly with jQuery’s $.animate(), $.fade(), and $.delay(). Since Velocity’s syntax is identical to $.animate(), your code doesn’t need to change. Secret Sauce
JavaScript and jQuery are falsely conflated. JavaScript animation, which Velocity uses, is fast; it’s jQuery that’s slow. Although Velocity works alongside jQuery, it uses its own animation stack that delivers its performance through two underlying principles: 1) synchronize the DOM → tween stack to minimize layout thrashing, and 2) cache values to minimize DOM querying.

Bitbucket Set up an SSH key on Sourcetree for Windows – Atlassian Documentation

Goto heading “Set up SSH with Sourcetree on Windows”‘
Source: Set up an SSH key – Atlassian Documentation


Also see this fix for getting PuTTY Pageant working with Visual Studio 2017 built-in GIT:
I finally managed to make it work, using PuTTY’s Pageant authentication agent instead of ssh-agent, and following the steps mentioned here (it’s for Visual Studio Code, but works for Visual Studio 2017 and I guess it should work for any application that uses the “official” Git for Windows).

Since I already had Pageant installed and a .ppk private key created, I only had to make Git use Pageant, by creating the GIT_SSH Windows environment variable and setting it to the path of the “plink.exe” file (inside the PuTTY installation, for example C:\Program Files (x86)\PuTTY\plink.exe). With that done, I just need to open Pageant and add the private key (and leave it open while working with the repository), and Visual Studio will be able to connect and issue commands just fine.
Fromhttps://stackoverflow.com/questions/42773636/connect-to-git-repository-with-ssh-using-visual-studio-2017#

Different js scripts for different ASP.NET core environments· jonhilton.net – Making sense of .NET

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

Three Steps For Increasing The Security of Your Web Apps – DEV Community 👩‍💻👨‍💻

Source: Three Steps For Increasing The Security of Your Web Apps – DEV Community 👩‍💻👨‍💻

Also have a look at OWASP Top 10 Most Critical Web Application Security Risks: https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project

 

Visual Studio Extension – Live Sass Compiler

Really simple and useful when working with sass files in Visual Studio Code.
Install from link below.
Click “Watch sass” in lower right corner of Visual Studio Code.
Edit an scss file and save. -> compiles to css file in the same directory. Also works with live browser reload. See output window / extensions / Live Sass Compile for process info.

Source: Live Sass Compiler – Visual Studio Marketplace

Continuous deployment to Azure in Visual Studio Team Service

> Hosting on Azure and building on Visual Studio Team Services (VSTS)? You should utilize the (now) wonderful release management tool built into VSTS.
blog.elmah.io/continuous-deployment-to-azure-in-visual-studio-team-service/?utm_campaign=dotNET%20Weekly&utm_medium=email&utm_source=week-36_year-2018

NLog vs log4net vs Serilog: Compare .NET Logging Frameworks

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