dotnet-proj-info
Features
- get properties
- get
fsc
/csc
command line arguments - get project to project references
- list installed .NET Framework versions
- get references path of .NET asseblies like
System
,System.Data
Support both project sdk:
- dotnet/sdk style projects (slim proj, usually .net core)
- old sdk projects (verbose proj, usually .NET)
Works on mono and windows .NET, and allow to specify the dotnet
(.NET Core) or msbuild
(.NET) to use
as .NET Tool
Install with:
dotnet tool install -g dotnet-proj
and
dotnet proj --help
Usage:
dotnet-proj.
USAGE: dotnet-proj [--help] [--verbose] [<subcommand> [<options>]]
SUBCOMMANDS:
prop <options> get properties
fsc-args <options> get fsc arguments
csc-args <options> get csc arguments
p2p <options> get project references
net-fw <options> list the installed .NET Frameworks
net-fw-ref <options> get the reference path of given .NET Framework assembly
Use 'dotnet-proj <subcommand> --help' for additional information.
OPTIONS:
--verbose, -v verbose log
--help display this list of options.
Subcommands support usual arguments of .NET cli (dotnet
) where make sense, like:
- the project to use
-c
or--configuration
-f
or--framework
-r
or--runtime
See examples directory for a quick tutorial
as Library
Used by:
- Fable compiler to parse fsproj projects with
dotnet fable
- FsAutocomplete (FSAC) to parse projects. That's the language server that add F# support in:
Build
Clone repo.
Run:
dotnet build
To run tests:
# create packages first (see below)
dotnet test -v n
To create packages:
dotnet pack
will create packages in bin\nupkgs
pass /p:Version=1.2.3
to create a package with version 1.2.3
Release
Make a new version tag and push that to the repo. Appveyor builds that are based off tags will create a github release. Nuget packages need to be pushed separately, but can be downloaded from Appveyor to do so.