Hi there,
I’ve had some persistent issues with using Yak. While I can generate a working .yak package containing a RhinoCommon plugin (.rhp), the details of the package as described in the manifest.yml don’t get populated in the PackageManager, and the version selection dropdown is always left empty.
I’ve even tried simply using the RhinoCommon (C#) template in Visual Studio which contains an option for generating the Yak packaging in the build step:
When I build the template project, and install the resulting .yak package, the PackageManager entry is unpopulated:
Note that while the generated manifest.yml contains an author and description:
- The Author section is empty
- The Version dropdown is empty
- The Description is empty
Here is the manifest info printed out during the packing process within Visual Studio:
1>Building package from contents of B:\Projects\Polaris3D\ReferenceProjects\YakPackageTest\YakPackageTest\bin\Debug
1>
1>Found manifest.yml for package: YakPackageTest (1.0.0)
1>Inspecting content: YakPackageTest.rhp
1>EXEC : warning : Content version doesn't match manifest: '1.0' != '1.0.0'
1>
1>Creating yakpackagetest-1.0.0-rh8_0-any.yak
1>
1>---
1>name: YakPackageTest
1>version: 1.0.0
1>authors:
1>- YakPackageTest Authors
1>description: Description of YakPackageTest
1>url: <url>
1>keywords: []
1>
For this example, I’m just using the Visual Studio template for RhinoCommon Plug-In for Rhino3D (C#) i.e.

However, if it’s helpful for troubleshooting, here is the resulting repo from my GitHub GitHub - dcondon-pmdi/YakPackageTest
Kind regards,
Dustin
If you check “Build Yak Package” it won’t use the manifest.yml but it will use attributes from the .rhp dll. You’ll need to either;
- Use the yak CLI tool to build if you want to use the
manifest.yml
- Add these attributes to your .csproj, take a look here for more → About Yak's manifest.yml - #10 by CallumSykes
Thanks for the reply!
I have experimented a fair amount with both using the generated manifest.yml and writing my own manifest.yml file. Using either method, I’ve so far been unable to have the PackageManager entry work correctly.
Following #2 that you suggested, I’ve bumped the version and set the properties in the csproj file to these:
<PropertyGroup>
<!-- Specifies information for Assembly and Yak -->
<Version>1.0.1</Version>
<Title>YakPackageTest</Title>
<Company>YakPackageTest Authors</Company>
<Description>Description of YakPackageTest</Description>
<Authors>MyCompany</Authors>
<Product>YakPackageTest</Product>
<Url>mywebsite.com</Url>
</PropertyGroup>
Note I’ve added the mywebsite.com property, which does get picked up when yak is building the package (i.e. this is part of the console output from Visual Studio after the build):
1>
1>Creating yakpackagetest-1.0.1-rh8_0-any.yak
1>
1>---
1>name: YakPackageTest
1>version: 1.0.1
1>authors:
1>- MyCompany
1>description: Description of YakPackageTest
1>url: mywebsite.com
1>keywords: []
1>
However, the PackageManager entry is still empty, including the Url entry.
Can you drop the yak package here?
Yup can do:
yakpackagetest-1.0.1-rh8_0-any.yak (17.0 KB)
Let me know if you need any other info.
Yak packages aren’t some fancy file format, they’re just renamed zips so let’s look inside.
- rhp / frameworks look correct
- Manifest.yml has data in it that SHOULD populate that ui
- yml is valid
- Changing manifest.yml attributes and/or version does nothing.
- 8 and 9 show nothing
- Brand new project with
--yak and same deal
I will look into this further, thanks for the report @Dustin_Condon
Apparently this never worked! I remember it working, but apparently my memory is fallible.
Here’s a ticket to get it working → https://mcneel.myjetbrains.com/youtrack/issue/RH-89957/Yaks-without-package-sources-do-not-fill-out-info
If you want a workaround, you can add any folder that has yaks in it to Rhinos package sources. Settings found in Options > Advanced Settings.
And then the info will appear.
Aha! Thank you for looking into it so fast!