import React, { useState } from "react";
export const Input = () => {
const [name, setName] = useState("");
return <input value={name} onChange={(e) => setName(e.target.value)} />;
}; const [name, setName] = useState(0);
const [name, setName] = useState<string>(""); const [name, setName] = useState(""); const [name, setName] = useState<string | null>(null);
import React, { useRef, useState } from "react";
export const Input = () => {
const [name, setName] = useState("");
const inputRef = useRef(null);
if (inputRef && inputRef.current) {
console.log("ref", inputRef.current.value);
}
return (
<input
ref={inputRef}
value={name}
onChange={(e) => setName(e.target.value)}
/>
);
}; 
interface MutableRefObject<T> {
current: T;
} const inputRef = useRef<HTMLInputElement>(null);
//if (inputRef && inputRef.current) {
console.log("ref", inputRef.current.value);
//} 
console.log("ref", inputRef?.current?.value); # Get the emsdk repo git clone https://github.com/emscripten-core/emsdk.git # Enter that directory cd emsdk # Download and install the latest SDK tools. emsdk install latest # Make the "latest" SDK "active" for the current user. (writes .emscripten file) emsdk activate latest # Activate PATH and other environment variables in the current terminal emsdk_env.bat
C:\Users\{your pc name}\emsdk emcc C:\Users\{your pc name}\sqlite\sqlite3.c -shared -o D:\e_sqlite3.o warning : @(NativeFileReference) is not empty, but the native references won't be linked in, because neither $(WasmBuildNative), nor $(RunAOTCompilation) are 'true'. NativeFileReference=Data\e_sqlite3.o [D:\project\Yourproject\Yourproject.csproj] 1 Warning(s)
<RunAOTCompilation>true</RunAOTCompilation>
<PropertyGroup>
dotnet workload install wasm-tools
با تشکر.
PM> install-package AutoMapper PM> install-package EntityFramework
public class BlogPost
{
public int Id { get; set; }
public string Title { get; set; }
public string Content { get; set; }
[ForeignKey("UserId")]
public virtual User User { get; set; }
public int UserId { get; set; }
}
public class User
{
public int Id { get; set; }
public string Name { get; set; }
public int Age { get; set; }
public virtual ICollection<BlogPost> BlogPosts { get; set; }
} public class UserViewModel
{
public int Id { set; get; }
public string Name { set; get; }
public ICollection<BlogPost> BlogPosts { get; set; }
} public class TestProfile : Profile
{
protected override void Configure()
{
this.CreateMap<User, UserViewModel>();
}
public override string ProfileName
{
get { return this.GetType().Name; }
}
} Mapper.Initialize(cfg => // In Application_Start()
{
cfg.AddProfile<TestProfile>();
}); using (var context = new MyContext())
{
var user1 = context.Users.FirstOrDefault();
if (user1 != null)
{
var uiUser = new UserViewModel();
Mapper.Map(source: user1, destination: uiUser);
Console.WriteLine(uiUser.Name);
foreach (var post in uiUser.BlogPosts)
{
Console.WriteLine(post.Title);
}
}
} var user1 = context.Users.Include(user => user.BlogPosts).FirstOrDefault();
var uiUser = context.Users.Project().To<UserViewModel>().FirstOrDefault();
باید عرض کنم بله وقتی کاربری یافت نشد چه کاری میتوانیم انجام دهیم؟
Errors should be handled via exceptions, but successes shouldn't
The typical meaning of the word "exception" is an event that is unexpected rather than part of normal operation; otherwise people would just say "event"
Methods should have a way to indicate various kinds of results. Whether those results are treated as exceptional should depend on the caller.
We are going to talk about:
What you get out of the box with ASP.NET Core 2.0
How to use Postman to test your API
Changing the default configuration of our project
Testing the content negotiation
Restricting media types
More about formatters
Implementing a custom formatter
Consuming API programmatically
First, the decoupling of .NET from Windows
Second, the newfound focus on CLR performance
Third, moving .NET’s tooling to a cross-platform model
Fourth, the .NET user base is embracing the OSS ecosystem as a whole
Fifth, in general the direction on .NET development is pushing users further down into the details of the stack
Sixth, Microsoft’s platform work being done out in the open
