Node.js Tools 1.0 for Visual Studio (NTVS) is now available for download! NTVS is a free, open source extension for Visual Studio 2012 and Visual Studio 2013 that turns Visual Studio into a Node.js IDE. NTVS 1.0 supports the free Visual Studio Community and Visual Studio Express for Web editions, as well as Visual Studio Professional and higher
git log --oneline
Install-Module -Name Microsoft.PowerShell.Crescendo
$Configuration = @{
'$schema' = "https://aka.ms/PowerShell/Crescendo/Schemas/2021-11"
Commands = @()
}
$parameters = @{
Verb = "Get"
Noun = "GitLog"
OriginalName = "git"
}
$Configuration.Commands += New-CrescendoCommand @parameters
$Configuration | ConvertTo-Json -Depth 3 | Out-File ./git-ps.json {
"Commands": [
{
"Verb": "Get",
"Noun": "GitLog",
"OriginalName": "git",
"OriginalCommandElements": null,
"Platform": [
"Windows",
"Linux",
"MacOS"
],
"Elevation": null,
"Aliases": null,
"DefaultParameterSetName": null,
"SupportsShouldProcess": false,
"ConfirmImpact": null,
"SupportsTransactions": false,
"NoInvocation": false,
"Description": null,
"Usage": null,
"Parameters": [],
"Examples": [],
"OriginalText": null,
"HelpLinks": null,
"OutputHandlers": null
}
],
"$schema": "https://aka.ms/PowerShell/Crescendo/Schemas/2021-11"
} "": "https://aka.ms/PowerShell/Crescendo/Schemas/2021-11",
اکنون باید این فایل Configuration را به Crescendo معرفی کنیم تا cmdlet را برایمان تولید کند. اینکار را توسط Export-CrescendoModule انجام خواهیم داد:
Export-CrescendoModule -Configuration ./git-ps.json -ModuleName ./git-ps.psm1
با اجرای دستور فوق، فایل‌های git.psm1 و همچنین git.psd1 تولید خواهند شد. نیاز به بررسی فایل‌های جنریت شده نیست؛ چون تنها جایی که با آن باید در ارتباط باشیم، همان فایل JSON ابتدای بحث است که در ادامه آن را بررسی خواهیم کرد. اما قبل از آن اجازه دهید ماژول تولید شده را Import کنیم و دستور Get-GitLog را وارد کنیم:
PP /> Import-Module ./git-ps.psd1
PS /> Get-GitLog
usage: git [-v | --version] [-h | --help] [-C <path>] [-c <name>=<value>]
[--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]
[-p | --paginate | -P | --no-pager] [--no-replace-objects] [--bare]
[--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]
[--super-prefix=<path>] [--config-env=<name>=<envvar>]
<command> [<args>]
These are common Git commands used in various situations:
start a working area (see also: git help tutorial)
clone Clone a repository into a new directory
init Create an empty Git repository or reinitialize an existing one
work on the current change (see also: git help everyday)
add Add file contents to the index
mv Move or rename a file, a directory, or a symlink
restore Restore working tree files
rm Remove files from the working tree and from the index
examine the history and state (see also: git help revisions)
bisect Use binary search to find the commit that introduced a bug
diff Show changes between commits, commit and working tree, etc
grep Print lines matching a pattern
log Show commit logs
show Show various types of objects
status Show the working tree status
grow, mark and tweak your common history
branch List, create, or delete branches
commit Record changes to the repository
merge Join two or more development histories together
rebase Reapply commits on top of another base tip
reset Reset current HEAD to the specified state
switch Switch branches
tag Create, list, delete or verify a tag object signed with GPG
collaborate (see also: git help workflows)
fetch Download objects and refs from another repository
pull Fetch from and integrate with another repository or a local branch
push Update remote refs along with associated objects
'git help -a' and 'git help -g' list available subcommands and some
concept guides. See 'git help <command>' or 'git help <concept>'
to read about a specific subcommand or concept.
See 'git help git' for an overview of the system. همانطور که مشاهده میکنید، خروجی دستور git، نمایش داده شده‌است. دلیل آن نیز این است که در فایل configuration، هیچ آرگومانی را به عنوان ورودی آن تعیین نکرده‌ایم. برای اضافه کردن آرگومان‌های موردنظر باید پراپرتی OrginalCommandElements را مقدار دهی کنیم:
"OriginalCommandElements": ["log", "--oneline"],
بنابراین با فراخوانی دستور Get-GitLog، در اصل دستور git log —oneline فراخوانی خواهد شد:
PS /> Get-GitLog e9590e8 init
اما تا اینجا نیز خروجی به صورت رشته‌ایی است. برای داشتن یک خروجی Object، باید پراپرتی OutputHandlers را از Configuration، تغییر دهیم:
"OutputHandlers": [
{
"ParameterSetName": "Default",
"Handler": "$args[0] | ForEach-Object { $hash, $message = $_.Split(' ', 2) ; [PSCustomObject]@{ Hash = $hash; Message = $message } }"
}
] در اینجا توسط args$ به خروجی کامند اصلی دسترسی خواهیم داشت. این خروجی را سپس با کمک ForEach-Object، به یک شیء با پراپرتی‌های Hash و Message تبدیل کرده‌ایم. در اینجا فقط میخواستم روال تهیه یک آبجکت را از کامندهایی که خروجی JSON ندارند، نشان دهم؛ اما خوشبختانه توسط پرچم pretty در git log، امکان تهیه‌ی خروجی JSON را نیز داریم:
git log --pretty=format:'{"commit": "%h", "author": "%an", "date": "%ad", "message": "%s"}' در نتیجه عملاً نیازی به split کردن نیست و بجای آن میتوانیم به صورت مستقیم، خروجی را توسط ConvertFrom-Json پارز کنیم:
"OutputHandlers": [
{
"ParameterSetName": "Default",
"Handler": "$args[0] | ConvertFrom-Json"
}
] همچنین درون فایل schema با کمک پراپرتی Parameters، امکان تعریف پارامتر را نیز برای کامند Get-GitLog خواهیم داشت. به عنوان مثال میتوانیم فلگ reverse را نیز به کامند اصلی از طریق PowerShell ارسال کنیم:
"Parameters": [
{
"Name": "reverse",
"OriginalName": "--reverse",
"ParameterType": "switch",
"Description": "Reverse the order of the commits in the output."
}
], دقت داشته باشیم که با هربار تغییر فایل schema باید توسط دستور Export-CrescendoModule ماژول موردنظر را تولید کنید:
Export-CrescendoModule -Configuration ./git-ps.json -ModuleName ./git-ps.psm1 Import-Module ./git-ps.psd1
در نهایت cmdletمان به این صورت قابل استفاده خواهد بود:
dotnet new mvc
ng new SignalRCore2Client
<Project Sdk="Microsoft.NET.Sdk.Web">
<PropertyGroup>
<TargetFramework>netcoreapp2.0</TargetFramework>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="Microsoft.AspNetCore.All" Version="2.0.0" />
<PackageReference Include="Microsoft.AspNetCore.SignalR" Version="1.0.0-alpha1-final" />
</ItemGroup>
<ItemGroup>
<DotNetCliToolReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Tools" Version="2.0.0" />
<DotNetCliToolReference Include="Microsoft.DotNet.Watcher.Tools" Version="2.0.0" />
</ItemGroup>
</Project> dotnet restore
dotnet watch run
using System.Threading.Tasks;
using Microsoft.AspNetCore.SignalR;
namespace SignalRCore2WebApp.Hubs
{
public class MessageHub : Hub
{
public Task Send(string message)
{
return Clients.All.InvokeAsync("Send", message);
}
}
} public void ConfigureServices(IServiceCollection services)
{
services.AddSignalR();
services.AddMvc();
} public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
app.UseSignalR(routes =>
{
routes.MapHub<MessageHub>(path: "message");
}); http://localhost:5000/message
using System.Threading.Tasks;
using Microsoft.AspNetCore.Mvc;
using Microsoft.AspNetCore.SignalR;
using SignalRCore2WebApp.Hubs;
namespace SignalRCore2WebApp.Controllers
{
public class HomeController : Controller
{
private readonly IHubContext<MessageHub> _messageHubContext;
public HomeController(IHubContext<MessageHub> messageHubContext)
{
_messageHubContext = messageHubContext;
}
public IActionResult Index()
{
return View(); // show the view
}
[HttpPost]
public async Task<IActionResult> Index(string message)
{
await _messageHubContext.Clients.All.InvokeAsync("Send", message);
return View();
}
}
} @{
ViewData["Title"] = "Home Page";
}
<form method="post"
asp-action="Index"
asp-controller="Home"
role="form">
<div class="form-group">
<label label-for="message">Message: </label>
<input id="message" name="message" class="form-control"/>
</div>
<button class="btn btn-primary" type="submit">Send</button>
</form> npm install @aspnet/signalr-client --save
import { Component, OnInit } from "@angular/core";
import { HubConnection } from "@aspnet/signalr-client";
@Component({
selector: "app-root",
templateUrl: "./app.component.html",
styleUrls: ["./app.component.css"]
})
export class AppComponent implements OnInit {
hubPath = "http://localhost:5000/message";
messages: string[] = [];
ngOnInit(): void {
const connection = new HubConnection(this.hubPath);
connection.on("send", data => {
this.messages.push(data);
});
connection.start().then(() => {
// connection.invoke("send", "Hello");
console.log("connected.");
});
}
} <div>
<h1>
The messages from the server:
</h1>
<ul>
<li *ngFor="let message of messages">
{{message}}
</li>
</ul>
</div> ng serve -o
Failed to load http://localhost:5000/message: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:4200' is therefore not allowed access.
public void ConfigureServices(IServiceCollection services)
{
services.AddSignalR();
services.AddCors(options =>
{
options.AddPolicy("CorsPolicy",
builder => builder
.AllowAnyOrigin()
.AllowAnyMethod()
.AllowAnyHeader()
.AllowCredentials());
});
services.AddMvc();
} public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
app.UseCors(policyName: "CorsPolicy"); 
How to build a .NET Core Project with VS Code ?
Rider 2018.3.1 comes with fixes for:
Several issues in the debugger: RIDER-23087, RIDER-22932, RIDER-22770, RIDER-22887, and RIDER-22873.
Broken NuGet window after searching for “mongo” text (RIDER-22927).
Endless “Retrieving properties…” progress bar for Project Properties (RIDER-22924).
Inability to activate the dotTrace plugin via the License Server (RIDER-22876).
The “Failed to get the list of simulators” error on getting a list of iOS simulators (RIDER-22878).
The issue where a .jar setting file couldn’t be imported to Rider 2018.3 (RIDER-22823).
The misplaced position of inline parameter name hints (RIDER-22452).
Fixed
SqlLocalDB instance pipe name. #1433 Changed
SuppressInsecureTLSWarning to allow suppression of TLS security warning when using Encrypt=false in the connection string. #1457 
With millions of users, resulting in 75 billion package downloads per month, npm has undoubtedly been a huge success and npm 7 is now here (and will also come with Node.js 15.0 next week). Key features include workspaces, installation of peer dependencies, and support for yarn.lock.
After five alphas over the last nine months, Bootstrap Icons has officially gone stable with our v1.0.0 release! We’re now over 1,100 icons and are on track to add hundreds more in our upcoming minor releases. This has been a labor of love and I’m thrilled to ship this latest update.
