Miguel
/
Obsidean_VM
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Obsidean_VM/07 - Desarrolo de Proyectos.../Proyectos Visual Studio/Como usar PublicApiGenerato...

2.6 KiB
Raw Blame History 

generate-public-api --assembly "D:\Proyectos\VisualStudio\S7Explorer\bin\Debug\net8.0-windows\DotNetSiemensPLCToolBoxLibrary.dll" --target-frameworks "net8.0-windows" > api.txt

generate-public-api --assembly "C:\Users\migue\.nuget\packages\paddleocrsharp\4.5.0.1\lib\net8.0\PaddleOCRSharp.dll" --target-frameworks "net8.0-windows" > PaddleOCRSharpAPI.txt

generate-public-api --package Extended.Wpf.Toolkit --package-version 4.7.25104.5739 --target-frameworks "net5.0-windows" > Xceed.Wpf.Toolkit.txt --verbose

PublicApiGenerator.Tool:
  Public API generator tool that is useful for semantic versioning

Usage:
  PublicApiGenerator.Tool [options]

Options:
  --target-frameworks <TARGET-FRAMEWORKS>          Target frameworks to use to restore packages in. Must be a suitable target framework for executables like netcoreapp2.1. It is possible to specify multiple target frameworks like netcoreapp2.1;net461
  --assembly <ASSEMBLY>                            The assembly name including the extension (i.ex. PublicApiGenerator.dll) to generate a public API from in case in differs from the package name.
  --project-path <PROJECT-PATH>                    The path to the csproj that should be used to build the public API.
  --package <PACKAGE>                              The package name from which a public API should be created. The tool assumes the package name equals the assembly name. If the assembly name is different specify
  --package-version <PACKAGE-VERSION>              The version of the package defined in to be used.
  --package-source <PACKAGE-SOURCE>                Package source or feed to use (multiple allowed).
  --generator-version <GENERATOR-VERSION>          The version of the PublicApiGenerator package to use.
  --working-directory <WORKING-DIRECTORY>          The working directory to be used for temporary work artifacts. A temporary directory will be created inside the working directory and deleted once the process is done. If no working directory is specified the users temp directory is used.
  --output-directory <OUTPUT-DIRECTORY>            The output directory where the generated public APIs should be moved.
  --verbose <VERBOSE>
  --leave-artifacts <LEAVE-ARTIFACTS>              Instructs to leave the temporary artifacts around for debugging and troubleshooting purposes.
  --wait-time-in-seconds <WAIT-TIME-IN-SECONDS>    The number of seconds to wait for the API generation process to end. If multiple target frameworks are used the wait time is applied per target framework.
  --version                                        Display version information