public class UpperInvariantLookupNormalizer : ILookupNormalizer
identityOptionsUser.RequireUniqueEmail = true;
public override string Normalize(string key)
services.AddScoped<ILookupNormalizer, CustomNormalizer>(); services.AddScoped<UpperInvariantLookupNormalizer, CustomNormalizer>();
public class UserValidator<TUser> : IUserValidator<TUser> where TUser : class
public override async Task<IdentityResult> ValidateAsync(UserManager<User> manager, User user)
{
// First use the built-in validator
var result = await base.ValidateAsync(manager, user).ConfigureAwait(false);
var errors = result.Succeeded ? new List<IdentityError>() : result.Errors.ToList();
// Extending the built-in validator
validateEmail(user, errors);
validateUserName(user, errors);
return !errors.Any() ? IdentityResult.Success : IdentityResult.Failed(errors.ToArray());
} services.AddScoped<IUserValidator<User>, CustomUserValidator>(); services.AddScoped<UserValidator<User>, CustomUserValidator>();
public class PasswordValidator<TUser> : IPasswordValidator<TUser> where TUser : class
private static void setPasswordOptions(PasswordOptions identityOptionsPassword, SiteSettings siteSettings)
{
identityOptionsPassword.RequireDigit = siteSettings.PasswordOptions.RequireDigit;
identityOptionsPassword.RequireLowercase = siteSettings.PasswordOptions.RequireLowercase;
identityOptionsPassword.RequireNonAlphanumeric = siteSettings.PasswordOptions.RequireNonAlphanumeric;
identityOptionsPassword.RequireUppercase = siteSettings.PasswordOptions.RequireUppercase;
identityOptionsPassword.RequiredLength = siteSettings.PasswordOptions.RequiredLength;
} "PasswordOptions": {
"RequireDigit": false,
"RequiredLength": 6,
"RequireLowercase": false,
"RequireNonAlphanumeric": false,
"RequireUppercase": false
}, services.AddScoped<IPasswordValidator<User>, CustomPasswordValidator>(); services.AddScoped<PasswordValidator<User>, CustomPasswordValidator>();
public static void AddErrorsFromResult(this ModelStateDictionary modelStat, IdentityResult result)
public static string DumpErrors(this IdentityResult result, bool useHtmlNewLine = false)
[AjaxOnly, HttpPost, ValidateAntiForgeryToken] [ResponseCache(Location = ResponseCacheLocation.None, NoStore = true)] public async Task<IActionResult> ValidateUsername(string username, string email)
[AjaxOnly, HttpPost, ValidateAntiForgeryToken] [ResponseCache(Location = ResponseCacheLocation.None, NoStore = true)] public async Task<IActionResult> ValidatePassword(string password, string username)
IPasswordValidator<User> passwordValidator, IUserValidator<User> userValidator,
[Required(ErrorMessage = "(*)")]
[Display(Name = "نام کاربری")]
[Remote("ValidateUsername", "Register",
AdditionalFields = nameof(Email) + "," + ViewModelConstants.AntiForgeryToken, HttpMethod = "POST")]
[RegularExpression("^[a-zA-Z_]*$", ErrorMessage = "لطفا تنها از حروف انگلیسی استفاده نمائید")]
public string Username { get; set; } How do callbacks, promises and async/await compare to each other? This article shows the same scenario using each of these three techniques so you can see the differences and choose which appeals most to you.
A .NET guideline specifies that an application should never throw a NullReferenceException. However, many applications and libraries do. The NullReferenceException is the most common exception happening. That’s why C# 8 tries to get rid of it. With C# 8, reference types are not null be default. This is a big change, and a great feature. However, what about all the legacy code? Can old libraries be used with C# 8 applications, and can C# 7 applications make use of C# 8 libraries?
This article demonstrates how C# 8 allows mixing old and new assemblies.
I get asked super often how to become a Data Engineer. That's why I decided to start this cookbook with all the topics you need to look into.
"dependencies": {
// ...
"jssha": "^2.1.0",
// ...
}, <script src="node_modules/jssha/src/sha512.js"></script>
// map tells the System loader where to look for things
var map = {
// ...
'jssha': 'node_modules/jssha/src'
};
// packages tells the System loader how to load when no filename and/or no extension
var packages = {
// ...
'jssha': { main: 'sha512.js', defaultExtension: 'js' }
}; import { Component, OnInit } from '@angular/core';
var jsSHA = require("jssha"); // ==> loads `sha512.js` file dynamically using `systemjs.config.js` file definitions
//declare var jsSHA: any; // ==> this requires adding <script src="node_modules/jssha/src/sha512.js"></script> to the first page manually.
@Component({
templateUrl: 'app/using-third-party-libraries/untyped-sha.component.html'
})
export class UnTypedShaComponent implements OnInit {
hash: String;
ngOnInit(): void {
let shaObj = new jsSHA("SHA-512", "TEXT");
shaObj.update("This is a test");
this.hash = shaObj.getHash("HEX");
}
} <h1>SHA-512 Hash / UnTyped</h1>
<p>String: This is a test</p>
<p>HEX: {{hash}}</p> var jsSHA = require("jssha"); npm install -g typings typings install jssha --save --ambient
{
"ambientDependencies": {
// ...
"jssha": "registry:dt/jssha#2.1.0+20160317120654"
}
} /// <reference path="../typings/browser/ambient/jssha/index.d.ts" />
import { Component, OnInit } from '@angular/core';
//import { jsSHA } from "jssha";
import * as jsSHA from "jssha"; // ===> var jsSHA = require("jssha"); // ===> loads `sha512.js` file dynamically using `systemjs.config.js` file definitions
@Component({
templateUrl: 'app/using-third-party-libraries/typed-sha.component.html'
})
export class TypedShaComponent implements OnInit{
hash: String;
ngOnInit(): void {
let shaObj = new jsSHA("SHA-512", "TEXT");
shaObj.update("This is a test");
this.hash = shaObj.getHash("HEX");
}
} 
Asynchronous methods in the upcoming versions of Visual Basic and C# are a great way to get the callbacks out of your asynchronous programming. In this article, I’ll take a closer look at what the new await keyword actually does, starting at the conceptual level and working my way down to the iron.
We're going to use Dapper.NET on our project; that much is not in doubt. However, we're not going to start development with it, and it will not be the only ORM in use. The plan is to develop this project using Entity Framework, and later optimize to use Dapper.NET in certain scenarios where the system needs a performance boost.
