Avalon Camping Planet Mac OS

macOS applications are typically distributed in a .appapplication bundle. To make .NET Core and Avalonia projects work in a .app bundle, some extra legwork has to be done after your application has gone through the publishing process.

  1. Avalon Camping Planet Mac Os 11
  2. Avalon Camping Planet Mac Os Download
  1. Download the Best Free Audio Plugins. Synths, Reverbs, Compressors.and much more. Just click and download.
  2. Jun 03, 2019 In Avalon you can hang out on the privately owned Descanso Beach. There’s good snorkeling at Lovers’ Cove and at Casino Point (Avalon Underwater Park), a marine reserve that’s also the best shore dive. Another way to escape the throngs is by kayaking to the quiet coves along Catalina’s rocky coastline.

With Avalonia, you'll have a .app folder structure that looks like this:

Nov 26, 2020 Your Mac can have as little as 64GB of free storage space, but at least 128GB of free storage space provides the best experience. Automatic Windows updates require that much space or more. If you have an iMac Pro or Mac Pro with 128GB of memory (RAM) or more, your startup disk needs at least as much free storage space as your Mac has memory.

For more information on Info.plist, see Apple's documentation here.

Making the application bundle

There are a few options available for creating the .app file/folder structure. You can do this on any operating system, since a .app file is just a set of folders laid out in a specific format and the tooling isn't specific to one operating system. However, if you build on Windows outside of WSL, the executable may not have the right attributes for execution on macOS -- you may have to run chmod +x on the published binary output (the output generated by dotnet publish) from a Unix machine. This is the binary output that ends up in the folder MyApp.app/Contents/MacOS/, and the name should match CFBundleExecutable.

The .app structure relies on the Info.plist file being properly formatted and containing the right information. Make sure that:

  • The value of CFBundleExecutable matches the binary name generated by dotnet publish -- typically this is the same as your .dll assembly name without.dll.
  • CFBundleName is set to the display name for your application. If this is longer than 15 characters, set CFBundleDisplayName too.
  • CFBundleIconFile is set to the name of your icns icon file (including extension)
  • CFBundleIdentifier is set to a unique identifier, typically in reverse-DNS format -- e.g. com.myapp.macos.
  • NSHighResolutionCapable is set to true (<true/> in the Info.plist).
  • CFBundleVersion is set to the version for your bundle, e.g. 1.4.2.
  • CFBundleShortVersionString is set to the user-visible string for your application's version, e.g. Major.Minor.Patch.

More documentation on possible Info.plist keys is available here.

If at any point the tooling gives you an error that your assets file doesn't have a target for osx-64, add the following runtime identifiers to the top <PropertyGroup> in your .csproj:

Add other runtime identifiers as necessary. Each one should be separated by a semicolon (;).

Notes on the .app executable file

The file that is actually executed by macOS when starting your .app bundle will not have the standard .dll extension. If your publish folder contents, which go inside the .app bundle, do not have both a MyApp (exectuable) and a MyApp.dll, things are probably not generating properly, and macOS will probably not be able to start your .app properly.

Some recent changes in the way .NET Core is distributed and notarized on macOS have caused the MyApp executable (also called the 'app host' in the linked documentation) to not be generated. You need this file to be generated in order for your .app to function properly. To make sure this gets generated, do one of the following:

  • Add the following to your .csproj file:
  • Add -p:UseAppHost=true to your dotnet publish command.

dotnet-bundle

dotnet-bundle is a NuGet package that publishes your project and then creates the .app file for you.

You'll first have to add the project as a PackageReference in your project. Add it to your project via NuGet package manager or by adding the following line to your .csproj file:

After that, you can create your .app by executing the following on the command line:

You can specify other parameters for the dotnet msbuild command. For instance, if you want to publish in release mode:

Avalon Camping Planet Mac Os 11

or if you want to specify a different app name:

Instead of specifying CFBundleDisplayName, etc., on the command line, you can also specify them in your project file:

By default, dotnet-bundle will put the .app file in the same place as the publish output: [project directory]/bin/{Configuration}/netcoreapp3.1/osx-x64/publish/MyBestThingEver.app.

For more information on the parameters you can send, see the dotnet-bundle documentation.

If you created the .app on Windows, make sure to run chmod +x MyApp.app/Contents/MacOS/AppName from a Unix machine. Otherwise, the app will not start on macOS.

Manual

Avalon Camping Planet Mac Os Download

First, publish your application (dotnet publish documentation):

Create your Info.plist file, adding or modifying keys as necessary:

Mac

You can then create your .app folder structure as outlined at the top of this page. If you want a script to do it for you, you can use something like this (macOS/Unix):

If you created the .app on Windows, make sure to run chmod +x MyApp.app/Contents/MacOS/AppName from a Unix machine. Otherwise, the app will not start on macOS.

Signing Your App

Once you have your .app file created, you'll probably want to sign your app so that it can be notarized and distributed to your users without Gatekeeper giving you a hassle. Notarization is required for apps distributed outside the app store starting in macOS 10.15 (Catalina), and you'll have to enable hardened runtime and run codesign on your .app in order to notarize it successfully.

You'll need a Mac computer for this step, unfortunately, as we have to run the codesign command line tool that comes with Xcode.

Running codesign and enabling hardened runtime

Enabling hardened runtime is done in the same step as code signing. You have to codesign everything in the .app bundle under the Contents/MacOS folder, which is easiest to do with a script since there are a lot of files. In order to sign your files, you need an Apple developer account. In order to notarize your app, you'll need to do the following steps with a Developer ID certificate, which requires a paid Apple developer subscription.

You'll also need to have the Xcode command line tools installed. You can get those by installing Xcode and running it or by running xcode-select --install on the command line and following the prompts to install the tools

First, enable Hardened Runtime with exceptions by creating an MyAppEntitlements.entitlements file:

Then, run this script to do all the code signing for you:

The --options=runtime part of the codesign line is what enables the hardened runtime with your app. Because .NET Core may not be fully compatible with hardened runtime, we add some exceptions to use JIT-compiled code and allow for Apple Events to be sent. The JIT-compiled code exception is required to run Avalonia apps under hardened runtime. We add the second exception for Apple Events to fix an error that shows up in Console.app.

Note: Microsoft lists some other hardened runtime exceptions as being required for .NET Core. The only one that is actually needed to run an Avalonia app is com.apple.security.cs.allow-jit. The others may impose security risks with your application. Use with caution.

Once your app is code signed, you can verify that it signed properly by making sure that the following command outputs no errors:

Notarizing your software

Notarization allows your app to be distributed outside the macOS App Store. You can read more about it here. If you run into any issues during the process, Apple has a helpful document of potential fixes here.

For more information on customizing your notarization workflow and more flags you may need to send when running xcrun altool, check out Apple's documentation.

The following steps were modified from this StackOverflow post:

  1. Make sure your .app is code signed properly
  2. Stick your .app in a .zip file, e.g. MyApp.zip.
  3. Run xcrun altool --notarize-app -f MyApp.zip --primary-bundle-id com.unique-identifier-for-this-upload -u username -p password. You can use a password in your keychain by passing -p '@keychain:AC_PASSWORD', where AC_PASSWORD is the key. The account has to be registered as an Apple Developer.
  4. If the upload is successful, you'll get a UUID back for your request token like this: 28fad4c5-68b3-4dbf-a0d4-fbde8e6a078f
  5. You can check notarization status using that token like this: xcrun altool --notarization-info 28fad4c5-68b3-4dbf-a0d4-fbde8e6a078f -u username -p password. This could take some time -- eventually it will succeed or fail.
  6. If it succeeds, you have to staple the notarization to the app: xcrun stapler staple MyApp.app. You can validate this by running xcrun stapler validate MyApp.app.

Once notarization is complete, you should be able to distribute your application!

Note that if you distribute your app in a .dmg, you will want to modify the steps slightly:

  1. Notarize your .app as normal (in a .zip file)
  2. Add your notarized and stapled (xcrun stapler) app into the DMG (the DMG now has the notarized/stapled .app file inside of it).
  3. Notarize your .dmg file (same basic xcrun altool command, just with the .dmg file for the -f flag instead of the .zip)
  4. Staple the notarization to the .dmg file: xcrun stapler staple MyApp.dmg.