Over five years ago I released MvcFlash, and soon after I released the second iteration MvcFlash2. Don't let the terrible naming and versioning fool you, this is one of my favorite creations. As ASP.NET 5 starts to take root and MVC 6 blossoms, I begin to feel more confident about creating the next version of MvcFlash. Honestly, I can't see developing an MVC application without it. Before I do, I thought I would muse about the possible challenges ahead.
Input Validation for me is about validating the user input. Some people call "Name must not be empty" a business rule, I think about it as input validation. Business Rules validation is more complex, because a business rule for me is not "Name must not be empty", it is a definition of a state in the system that requires an action. Here is a definition of a business rule:
An order should be payed within 30 days, this duration can be extended, to a maximum of three times.
.NET Conf is a free, three-day, virtual developer event co-organized by the .NET community and Microsoft. This year .NET 5.0 will launch at .NET Conf 2020! Come celebrate and learn about the new release. We're also celebrating our 10th anniversary and we're working on a few more surprises. You won't want to miss this one.
Today, we are releasing React 17! We’ve written at length about the role of the React 17 release and the changes it contains in the React 17 RC blog post. This post is a brief summary of it, so if you’ve already read the RC post, you can skip this one.
نسخه نهایی Blazor WebAssembly 3.2.0 تا اواسط ماه May 2020 (ماه جاری) منتشر میشود
The Blazor WebAssembly Release Candidate is here! This release contains all of the features and improvements that we expect to release for the upcoming Blazor WebAssembly release. There are no more breaking changes planned at this point.
What’s behind the hype about Blazor?
For many years now I’ve advocated not using the repository pattern on top of an ORM such as Entity Framework. There are many reasons why that I’ll try and cover throughout this post based on ways that I’ve seen it implemented. Meaning, this post is talking about poorly implemented approaches or pitfalls that I’ve seen.
.NET Conf is a FREE, 3 day virtual developer event co-organized by the .NET community and Microsoft. This year .NET Core 3.0 will launch at .NET Conf 2019! Come celebrate and learn about the new release. You won't want to miss this one.
export const Button = ({ onClick }: Props) => {
return <button onClick={onClick}>Click Me</button>;
}; 
import React from "react";
type Props = {
onClick: (e: React.MouseEvent) => void;
};
export const Button = ({ onClick }: Props) => {
return <button onClick={onClick}>Click Me</button>;
}; <Button
onClick={(e) => {
e.preventDefault();
console.log(e);
}}
/> 
import React from "react";
type Props = {
onClick: (e: React.MouseEvent<HTMLButtonElement>) => void;
};
export const Button = ({ onClick }: Props) => {
return <button onClick={onClick}>Click Me</button>;
}; 
import React from "react";
type Props = {
onClick: (e: React.MouseEvent<HTMLButtonElement>) => void;
onChange?: (e: React.FormEvent<HTMLInputElement>) => void;
};
export const Button = ({ onClick, onChange }: Props) => {
return (
<>
<input onChange={onChange} />
<button onClick={onClick}>Click Me</button>
</>
);
}; {
"dependencies": {
"@types/react": "^16.9.35",
"@types/react-dom": "^16.9.8",
}, import React, { FormEvent } from "react";
type Props = {
onChange?: (e: FormEvent<HTMLInputElement>) => void;
}; <Button
onClick={(e) => {
e.preventDefault();
console.log(e);
}}
>
Hello world!
</Button> import React, { FormEvent } from "react";
type Props = {
onClick: (e: React.MouseEvent<HTMLButtonElement>) => void;
onChange?: (e: FormEvent<HTMLInputElement>) => void;
children: string;
};
export const Button = ({ onClick, onChange, children }: Props) => {
return (
<>
<input onChange={onChange} />
<button onClick={onClick}>{children}</button>
</>
);
}; <Button
onClick={(e) => {
e.preventDefault();
console.log(e);
}}
>
<img src={logo} className="App-logo" alt="logo" />
</Button> 
import React, { FormEvent } from "react";
type Props = {
onClick: (e: React.MouseEvent<HTMLButtonElement>) => void;
onChange?: (e: FormEvent<HTMLInputElement>) => void;
// children: HTMLImageElement;
};
export const Button: React.FC<Props> = ({ onClick, onChange, children }) => {
return (
<>
<input onChange={onChange} />
<button onClick={onClick}>{children}</button>
</>
);
}; 
The two most important topics I want to focus on in this post are:
We have different options for each of them: You can go with Monorepos or Polyrepos for hosting your code, and you can pick different versioning methods like Semantic Release, Manual Versioning, Global Versioning, etc. I'll talk about each of them in the next sections.
Today, we are releasing updates to the .NET Core SDK, included in Visual Studio 2017 RC. You can also install the .NET Core SDK for use with Visual Studio Code or at the command line, on Windows, Mac and Linux. Check out the Visual Studio blog to learn more about this Visual Studio 2017 update.
