How to become a Zero to Hero in Unit Testing with C# and xUnit ?
Timeline:
Background 0:00:00
Introduction To Fluent Assertions 0:01:12
Setting Up Fluent Assertions 0:02:39
Basic Assertions with Fluent Assertions 0:09:19
Advanced Assertions with Fluent Assertions 0:20:28
Custom Assertions with Fluent Assertions 0:28:32
Test the Custom Person Assertions 0:47:56
Best Practices For Using Fluent Assertions 0:54:21
I always love talking to Julie! She first spends some time discussing some of the new things in Entity Framework 7 and when one should consider using (and more importantly not using) the new bits. She also gets into her experience working with Aurelia and node.js. Enjoy!
using (var scope = new TransactionScope(...))
{
using (var context = new YourContext(...))
{
var wallet =
context.ExecuteStoreQuery<UserWallet>("SELECT UserId, WalletId, Balance FROM UserWallets WITH (UPDLOCK) WHERE ...");
// your logic
scope.Complete();
}
} Asp.Net Core WebSockets Vs SignalR. Which should you use? (Full Course)
In this video we build 2 separate chat applications, one using Asp.Net Core WebSockets and the other using SignalR, allowing you to compare approaches and decide on which one works best for you. In both cases we build them with C#, .NET Core and JavaScript. You’ll also learn about:
- .NET Core Request Pipeline
- Request Delegates
- Asynchronous Programming in .NET (Async / Await)
- Introduction to Dependency Injection
Head.defaultProps = {
title: "Hello",
isActive: true
}; type Props = {
title: string;
isActive: boolean;
};
export const Head = ({ title = "Hello", isActive = true }: Props) => { 
type Props = {
title: string;
isActive?: boolean;
};
export const Head = ({ title, isActive = true }: Props) => { type User = {
name: string;
};
type Props = {
title: string;
isActive?: boolean;
count: number;
options: string[];
status: "loading" | "loaded";
thing: {};
thing2: {
name: string;
};
user: User;
func: () => void;
}; import React from "react";
type Props = {
// onClick(): string; method returns string
// onClick(): void method returns nothing;
// onClick(text: string): void; method with params
// onClick: () => void; function returns nothing
onClick: (text: string) => void; // function with params
};
export const Button = ({ onClick }: Props) => {
return <button onClick={() => onClick("hi")}>Click Me</button>;
}; import { Button } from "./components/Button";
import { Head } from "./components/Head";
// ...
function App() {
return (
<div className="App">
<Head title="Hello" />
<Button
onClick={(value) => {
console.log(value);
}}
/>
// ... IKVM.NET includes the following components:
The following new features are available for preview in this release:
Component architectures are an important part of ever modern front-end framework. In this article, I’m going to dissect Polymer, React, Rio.js, Vue.js, Aurelia and Angular 2 components. The goal is to make the commonalities between each solution obvious. Hopefully, this will convince you that learning one or the other isn’t all that complex, given that everyone has somewhat settled on a component architecture.
Partial views in ASP.NET MVC allow you to reuse and customise components to act like user controls. They consist of both code and markup. They are an idea that is easy to grasp but they have great potential for the more adventurous developer who is prepared to experiment. Dino Esposito explains
