dotnet-commands | NET Core apps as .NET CLI Commands

by Lambda3 C# Version: 0.5.2 License: Apache-2.0

X-Ray Key Features Code Snippets(3)Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | dotnet-commands Summary

dotnet-commands is a C# library. dotnet-commands has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

A tool that allows you to use .NET Core apps as .NET CLI Commands.

Support

Quality

Security

License

Reuse

Support

dotnet-commands has a low active ecosystem.

It has 8 star(s) with 4 fork(s). There are 7 watchers for this library.

It had no major release in the last 12 months.

There are 3 open issues and 13 have been closed. On average issues are closed in 7 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of dotnet-commands is 0.5.2

Quality

dotnet-commands has no bugs reported.

Security

dotnet-commands has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

dotnet-commands is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

dotnet-commands releases are available to install and integrate.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of dotnet-commands

Get all kandi verified functions for this library.

dotnet-commands Key Features

No Key Features are available at this moment for dotnet-commands.

dotnet-commands Examples and Code Snippets

.NET Commands,Running

Lines of Code : 18

License : Permissive (Apache-2.0)

Copy

.NET Commands

  Usage:
    dotnet commands install [@] [--force] [--pre] [--verbose]
    dotnet commands uninstall  [ --verbose]
    dotnet commands update ( | all) [--pre] [--verbose]
    dotnet commands (list|ls) [--verbose]
    dotnet commands --

.NET Commands,Installing,Powershell

Lines of Code : 1

License : Permissive (Apache-2.0)

Copy

&{$wc=New-Object System.Net.WebClient;$wc.Proxy=[System.Net.WebRequest]::DefaultWebProxy;$wc.Proxy.Credentials=[System.Net.CredentialCache]::DefaultNetworkCredentials;Invoke-Expression($wc.DownloadString('https://raw.githubusercontent.com/Lambda3

.NET Commands,Installing,CMD

Lines of Code : 1

License : Permissive (Apache-2.0)

Copy

@powershell -NoProfile -ExecutionPolicy unrestricted -Command "&{$wc=New-Object System.Net.WebClient;$wc.Proxy=[System.Net.WebRequest]::DefaultWebProxy;$wc.Proxy.Credentials=[System.Net.CredentialCache]::DefaultNetworkCredentials;Invoke-Expressio

Community Discussions

Trending Discussions on dotnet-commands

What nuget version is used by dotnet CLI /when do nuget features make it into the dotnet CLI?

QUESTION

What nuget version is used by dotnet CLI /when do nuget features make it into the dotnet CLI?

Asked 2020-Mar-20 at 10:23

I have both a specific and a broader question, and I'll use the specific one to illustrate the broader:

My use case is that I want to use this feature Support pre release packages with floating versions, which will be available in Nuget 5.6, both for local development and in my CI/CD pipelines for my .NET Core applications

So basically I want to use this feature in combination with:

the standalone nuget.exe CLI (for local dev)
Visual Studio (for local dev)
dotnet CLI's dotnet restore command (for local dev and for my pipelines)

For (1), it's pretty simple, when 5.6 is released, I can use it.

For (2), I found on here that each Nuget 5.x version was available in Visual Studio 16.x, so I guess theres's a good chance, that, when Visual Studio 16.6 is out, nuget 5.6 will be used there as well. (Couldn't find any other docs specifying this)

For (3), I have no idea.

So my specific question/problem was: When will I be able to use package reference versions like "*-*" that will use the latest release or prerelease version available and be able to run a dotnet restore command that understands this? As soon as nuget 5.6 comes out?

I found here that

The only difference: dotnet restore is a convenience wrapper to invoke dotnet msbuild /t:Restore which invokes an MSBuild-integrated restore. This only works on MSBuild distributions that include NuGet, such as Visual Studio 2017 (full Visual Studio, build tools) or Mono 5.2+ (=> msbuild /t:Restore) and the .NET Core SDK which provides this convenience command.

but again, which nuget version is used?

But my broader question coming from this is: What nuget version does the dotnet CLI use? Can you even say it uses a specific "version" or does it just contain a certain subset of features of nuget that do not really correspond to a version? Is there any documentation/process specifying when features of nuget make it into the dotnet CLI?

...

ANSWER

Answered 2020-Mar-20 at 10:23

What nuget version does the dotnet CLI use? Can you even say it uses a specific "version" or does it just contain a certain subset of features of nuget that do not really correspond to a version?

Since Net Core 2.1, dotnet cli contains partial nuget.exe cli functionality subsets rather than full nuget.exe cli, such as package projects, push packages, delete packages, restore packages, and so on.

Each dotnet cli corresponds to a version of the nuget.exe cli.

In fact, every net core sdk version will integrate some of the functionality of the corresponding version of nuget.exe cli and then renamed it as its special nuget version.

For an example, Net Core 3.1 sdk integrate part of nuget exe 5.5.0 functions and then make its own dotnet nuget version called 5.5.0.4(you see it by call dotnet nuget --version in CMD) while the related nuget.exe cli version is 5.5.0.6382.

Ultimately, the functions between them are the same, but different version numbers are set to distinguish them.

Nuget.exe cli version:

dotnet nuget version

And Net Core 3.0 sdk integrates part of nuget.exe 5.3.1.6368 and create its own dotnet nuget version 5.3.0.1 as a result.

Actually, you can see the nuget targets file and the corresponding function DLLs in this section under this path: C:\Program Files\dotnet\sdk\3.1.200 and you can see these parts of nuget functions.

Source https://stackoverflow.com/questions/60756934

Community Discussions, Code Snippets contain sources that include Stack Exchange Network