jonasalbert jonasalbert

## Dust.js
http://www.dustjs.com/guides/getting-started/

## torrent pluralsight - ASP.net
http://tparser.org/Pluralsight-ASP.NET

## Read .json in ASP.NET Core
https://stackoverflow.com/questions/31453495/how-to-read-appsettings-values-from-config-json-in-asp-net-core
https://stackoverflow.com/questions/41738692/read-appsettings-json-in-main-program-cs


## learnentityframeworkcore
http://www.learnentityframeworkcore.com/

## SOLID principles
https://www.codeproject.com/Articles/703634/SOLID-architecture-principles-using-simple-Csharp

## EF Corre - CodeFirst
https://www.devart.com/dotconnect/sqlite/docs/Tutorial_EFCore.html

## core - unit of work pattern
https://dotnetthoughts.net/implementing-the-repository-and-unit-of-work-patterns-in-aspnet-core/

## Hide Keyboard : UITableViewController
override func viewDidLoad() {
    super.viewDidLoad()
    tableView.keyboardDismissMode = UIScrollViewKeyboardDismissMode.onDrag
}

## Implement Events in Swift
http://blog.scottlogic.com/2015/02/05/swift-events.html

I initially started writing a blog post that discussed various alternatives to Key-Value-Observing (KVO) in Swift, however, I found myself writing more about the task of implementing events in Swift. So, I’ve decided to split the problem in two, in this post I’ll cover events, and I’ll follow-up with the KVO post later on.

I’m certainly not the first to blog about this topic, Mike Ash published a great article on Swift implementation of NSNotification just last week. However, in this post I’d like to approach the problem in a slightly different way, starting with a naïve implementation.

Let’s start at the beginning …

WHAT ARE EVENTS?
Cocoa has a number of techniques that allow classes to collaborate in a loosed-coupled fashion via some form of notification, including target-action, the delegate pattern, NSNotification and KVO. These are all forms of the classic Observer Pattern, yet all are different implementations, and each have their own failings.

## Core Data Migrations
https://www.raywenderlich.com/174025/lightweight-migrations-in-core-data-tutorial
	https://stackoverflow.com/questions/31453495/how-to-read-appsettings-values-from-config-json-in-asp-net-core
	https://stackoverflow.com/questions/41738692/read-appsettings-json-in-main-program-cs
	override func viewDidLoad() {
	super.viewDidLoad()
	tableView.keyboardDismissMode = UIScrollViewKeyboardDismissMode.onDrag
	}
	http://blog.scottlogic.com/2015/02/05/swift-events.html

	I initially started writing a blog post that discussed various alternatives to Key-Value-Observing (KVO) in Swift, however, I found myself writing more about the task of implementing events in Swift. So, I’ve decided to split the problem in two, in this post I’ll cover events, and I’ll follow-up with the KVO post later on.

	I’m certainly not the first to blog about this topic, Mike Ash published a great article on Swift implementation of NSNotification just last week. However, in this post I’d like to approach the problem in a slightly different way, starting with a naïve implementation.

	Let’s start at the beginning …

	WHAT ARE EVENTS?
	Cocoa has a number of techniques that allow classes to collaborate in a loosed-coupled fashion via some form of notification, including target-action, the delegate pattern, NSNotification and KVO. These are all forms of the classic Observer Pattern, yet all are different implementations, and each have their own failings.