Installing MauroContSysEdit.cli on Windows x64
Instructions for installing the MauroContSysEdit.cli command-line tool on Windows systems with x64 architecture.
Before installing MauroContSysEdit.cli on Windows x64, ensure you have:
- Windows 10 version 1809 or later, or Windows 11
- Administrator privileges (for system-wide installation)
- At least 100 MB of available disk space
- .NET 9 Runtime (or the self-contained version includes this)
There are three methods for installing the CLI on Windows x64: using a pre-built binary, building from source, or using the self-contained package.
-
Choose your installation method
- Download the pre-built binary from the GitHub releases page
- Build from source using the .NET SDK
- Use a self-contained published package
-
For pre-built binary installation:
- Navigate to the GitHub releases page at https://github.com/oughnic/Mauro-Edit/releases
-
Download the latest
MauroImportExport.Cli-win-x64.zipfile - Extract the ZIP archive to your desired installation directory (e.g., C:\Program Files\MauroContSysEdit.cli)
- Add the installation directory to your system PATH environment variable
-
For building from source:
- Install the .NET 9 SDK from https://dotnet.microsoft.com/download
-
Clone the repository:
git clone https://github.com/oughnic/Mauro-Edit.git -
Navigate to the CLI project directory:
cd Mauro-Edit/MauroImportExport.Cli -
Build the project:
dotnet build -c Release - The executable will be located in bin\Release\net9.0\
-
For self-contained package:
- Clone the repository and navigate to the CLI project directory
-
Publish as self-contained:
dotnet publish -c Release -r win-x64 --self-contained true - The self-contained package will be in bin\Release\net9.0\win-x64\publish\
- Copy the entire publish directory to your installation location
-
Verify the installation by opening a command prompt and running:
MauroImportExport.Cli.exe versionYou should see the CLI version information and available plugins.
MauroContSysEdit.cli is now installed on your Windows x64 system and ready to use.
Consider configuring logging options by setting the following assembly metadata in your environment or command-line options:
--log-fileto specify a log file location--log-levelto set the minimum logging level (Trace, Debug, Information, Warning, Error, Critical, None)