#
dotnet-cli
Here are 106 public repositories matching this topic...
Open
Documentation - Faq
1
mzorec
commented
Apr 21, 2020
Faq page will be added to https://flubucore.dotnetcore.xyz/
If anyone have a proposition about what to add to FAQ page please leave a comment in this issue.
2
bencz
commented
Oct 2, 2018
Hi!
It's possible to add, to automatic generate a version of WebApi with auth ( JWT for example ) and policys ?
Cross platform code coverage tool for .NET Core
-
Updated
Jun 13, 2020 - C#
A command-line tool that enables quick build and run deployments over SSH.
ssh
raspberry-pi
monitor
deployer
continuous-integration
continuous-delivery
continuous-deployment
dotnet-core
raspbian
dotnet-cli
dotnet-framework
raspberry-pi-3
continuous-release
-
Updated
Mar 3, 2020 - C#
[DEPRECATED] F# and .NET Core SDK working together
-
Updated
Jan 8, 2019 - C#
Modern .NET tools and library for XDT (Xml Document Transformation)
-
Updated
Mar 24, 2020 - C#
-
Updated
Apr 17, 2019 - C#
FlexCLI is a C++/CLI interface to access NVidia Flex from .Net environments like C#, IronPython, VB etc. FlexHopper is a plugin for Grasshopper built on top of FlexCLI
-
Updated
Dec 9, 2019 - C#
cmeeren
commented
Nov 6, 2019
It seems that currently, femto must be used for each project separately. It would be great if it could be used for all projects in a solution, and/or recursively for all projects in a subfolder.
.NET CLI template for Petabridge-style projects
-
Updated
May 28, 2020 - F#
MSBuild task and CLI tools for bundling .NET Core projects into MacOS applications (.app)
-
Updated
Apr 25, 2020 - C#
dotnet utility to run .net full apps using mono on OSX/Linux
-
Updated
Oct 2, 2019 - F#
Get info from .net sdk based msbuild projects ( https://github.com/dotnet/sdk ) or old sdk based projects (verbose fsproj)
-
Updated
Jun 10, 2020 - F#
.NET Core CLI tool to update the version information in .NET Core *.csproj files
-
Updated
Mar 5, 2020 - C#
A hook proof of concept with no native dependencies. Hook both .NET methods (even framework methods) and Native methods entirely in .NET.
-
Updated
Aug 1, 2018 - C#
.Net Core solution template using the cake build system.
-
Updated
Mar 27, 2020 - C#
PowerShell tab completion and tooltip support for the dotnet CLI.
-
Updated
Nov 27, 2017 - PowerShell
A dotnet CLI tool to work with GraphQL queries. It allows for static query verification and advanced type checking against a remote or local schema as well as code generating type-safe clients for F# and Fable.
-
Updated
Jun 7, 2020 - F#
rozele
commented
Sep 12, 2019
While we don't currently support any NLU providers that include multi-intent, we should document how multi-intent providers could be testing using the existing tools.
dotnet CLI minor mode for Emacs
-
Updated
Apr 15, 2019 - Emacs Lisp
CometD Salesforce Implementation.
salesforce
dotnet-core
cometd
dotnet-cli
workbench
salesforce-developers
salesforce-api
salesforce-rest-api
salesforce-apex
bay
-
Updated
May 4, 2020 - C#
Automatic versioning and CHANGELOG generation, using conventional commit messages
-
Updated
Jan 22, 2020 - C#
Test to build a multi-platforms Native NetStandard2.0 Nuget package using dotnet cli
-
Updated
May 28, 2020 - CMake
.NET CLI tool that can download .gitignore file from gitignore repository
-
Updated
Feb 20, 2020 - C#
Light-weight cross platform IL disassembler tool built in C#.
-
Updated
Feb 7, 2020 - C#
gulp plugin for the dotnet cli
-
Updated
Dec 28, 2019 - TypeScript
Publish your application to a Docker image using .NET Core CLI
-
Updated
Sep 26, 2016 - C#
SDK and command line utility for enumerate leaked credentials on the wild.
osint
toolkit
dotnet-core
cti
dotnet-cli
leaked-secrets
winget-pkg
choco-pkg
nuget-pkg
credential-cat
-
Updated
May 25, 2020 - C#
-
Updated
Feb 18, 2017 - C#
Improve this page
Add a description, image, and links to the dotnet-cli topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the dotnet-cli topic, visit your repo's landing page and select "manage topics."
@natemcmaster This repository is fantastic. Especially for a librarian junkie like me. However, .NET Core is getting so popular I wonder if things should be broken out differently?
Some possible starter categories