InfinitespaceStudios.MonoGame.Packaging 0.1.10-alpha

This is a prerelease version of InfinitespaceStudios.MonoGame.Packaging.
dotnet add package InfinitespaceStudios.MonoGame.Packaging --version 0.1.10-alpha                
NuGet\Install-Package InfinitespaceStudios.MonoGame.Packaging -Version 0.1.10-alpha                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="InfinitespaceStudios.MonoGame.Packaging" Version="0.1.10-alpha" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add InfinitespaceStudios.MonoGame.Packaging --version 0.1.10-alpha                
#r "nuget: InfinitespaceStudios.MonoGame.Packaging, 0.1.10-alpha"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install InfinitespaceStudios.MonoGame.Packaging as a Cake Addin
#addin nuget:?package=InfinitespaceStudios.MonoGame.Packaging&version=0.1.10-alpha&prerelease

// Install InfinitespaceStudios.MonoGame.Packaging as a Cake Tool
#tool nuget:?package=InfinitespaceStudios.MonoGame.Packaging&version=0.1.10-alpha&prerelease                

PackageCreator

Usage

  1. Add the Nuget package InfinitespaceStudios.MonoGame.Packaging to your DesktopGL project.

  2. Use the following to create a Mac Package

    msbuild <project> /p:Configuration=Release /t:Build /p:PackageTargetPlatforms=MacOS

This will produce an .app package in the $(OutputDir). Note you should run this command in the same directory as the csproj for your DesktopGL project. This will make sure the correct paths are used.

Packages will be created by default when you build your application. This behaviour can be disabled by the AutoBuildPackages property.

Available Targest

  • BuildGamePackages - Builds a number of Game packages based on the value of PackageTargetPlatforms. Will run automatically after a build.

  • SignGamePackages - This is for MacOS only. It will sign the .app package with the code signing certificate defined by PackageCodeSignCertificate. It will also produce a .pkg file and sign that using the PackageInstallerCertificate.

Available Properties

  • AutoBuildPackages - This boolean property controls if the packages are built. If you do not want to build packages for a debug build you can set this property to false in your debug configuration property group.

  • PackageTargetPlatforms - Controls which packages are created. Valid values are MacOS, Linux, Steam, Windows, ItchIo.

  • PackageIcon - The Icon to use for the package. It should be a decent resolution. This will be used as a basis for your MacOS app icon. Defaults to $(MSBuildProjectDirectory)\Icon.png if it exists.

  • PackageName - The name of the Final package. For example Foo.app or Foo.exe. Defaults to $(AssemblyName).

  • PackageDisplayName - The Dispay Name for the package. This is mostly for MacOS. Use this if you want to app name to be different from your Exe Name. For example For a exe called FooBar.exe you might want a Display Name of "Foo Bar!". Defaults to $(PackageName).

  • PackageId - The ID for the package. Again mostly for MacOS Defaults to com.yourdomain.$(PackageName).

  • PackageCopyright - Your copyright detalts. Defaults to Copyright © You This Year.

  • ContentDirectory - The location to pick up the built content. Defaults to $(OutputPath)Content.

  • OutputDirectory - The output path for the final packages. Defaults to $(OutputPath).

  • PackageSourceDirectory - The location to pick up the binaries for the package. Note it will only pick up the files in the directory. Sub directories will be ignored. If you have additional files make use of the PackageAdditionalAssemblies property. Defaults to $(OutputPath).

Advanced Properties

  • IncludeMcsInPackage - Controls if a mkbundled version of mcs (C# compiler) is included in the app packages. This only applies to Unix based packages. This should only be used if you find you need the compiler when deserializing data from disk.

  • PackageAdditionalAssemblies - Allows you to speficy additional assemblies to include into the final package.

  • PackageInstallerCertificate - The name of the Installer Certificate to use to sign the .pkg installer package.

  • PackageCodeSignCertificate - The name of the Code Signing Certificate to use to sign the .app bundle.

  • PackageCustomInfoPlist - Allows the developer too provide there own Info.plist for MacOS packaging. If not provided a default one will be created.

  • PackageCodeSignEntitlements - The relative path to Entitlements.plist from the current project directory.

There are no supported framework assets in this package.

Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
0.1.10-alpha 1,673 7/27/2018
0.1.9-alpha 717 7/25/2018
0.1.8-alpha 715 7/25/2018
0.1.7-alpha 739 7/24/2018
0.1.6-alpha 740 7/23/2018
0.1.5-alpha 744 7/23/2018
0.1.4-alpha 678 7/23/2018
0.1.3-alpha 672 7/23/2018
0.1.2-alpha 852 7/18/2018
0.1.1-alpha 737 6/20/2018
0.1.0-alpha 856 6/20/2018
0.0.9-alpha 797 6/20/2018
0.0.8-alpha 826 5/15/2018
0.0.7-alpha 881 2/13/2018
0.0.6-alpha 800 10/20/2017
0.0.5-alpha 836 10/18/2017
0.0.4-alpha 883 10/18/2017
0.0.3-alpha 879 10/18/2017
0.0.2-alpha 909 2/26/2017
0.0.1-alpha 931 2/25/2017

Fixed up some issues with codesigning the .app package.