About Yak's manifest.yml

Rhino Developer Yak
1

I created a project in Visual Studio without checking Build Yak Package.
Can the name and verison in manifest.yml be changed from VisualStudio during build?
Is the only way to do this is to open manifest.yml directly in a text editor and edit it?

  <Target Name="BuildYakPackage" AfterTargets="DispatchToInnerBuilds">
    <PropertyGroup>
      <YakExecutable Condition="$(YakExecutable) == '' and $([MSBuild]::IsOSPlatform(windows)) and Exists('C:\Program Files\Rhino 8\System\Yak.exe')">C:\Program Files\Rhino 8\System\Yak.exe</YakExecutable>
      <YakExecutable Condition="$(YakExecutable) == '' and $([MSBuild]::IsOSPlatform(macos)) and Exists('/Applications/Rhino 8.app/Contents/Resources/bin/yak')">/Applications/Rhino 8.app/Contents/Resources/bin/yak</YakExecutable>
      
      <BuildYakPackage Condition="$(BuildYakPackage) == '' and $(YakExecutable) != '' and Exists($(YakExecutable))">True</BuildYakPackage>
    </PropertyGroup>
    
    <Warning Text="Could not find Yak executable" Condition="$(YakExecutable) == ''" />

    <ItemGroup>
      <YakPackagesToDelete Include="$(OutputPath)\*.yak;$(OutputPath)\**\manifest.yml" />
    </ItemGroup>
    
    <Delete Files="@(YakPackagesToDelete)" />

    <Exec Command="&quot;$(YakExecutable)&quot; spec" WorkingDirectory="$(OutputPath)" Condition="$(BuildYakPackage) == 'True'" />
    <Exec Command="&quot;$(YakExecutable)&quot; build" WorkingDirectory="$(OutputPath)" Condition="$(BuildYakPackage) == 'True'" />

  </Target>

{DC5145E0-29FD-4D62-AD0F-99C9A86FD58C}

Changing this section will not make any difference.
Also, are the alphanumeric characters that are listed after the version always added?

{D144DE54-48F7-4CA8-A16A-E7E04849A4BA}
{D144DE54-48F7-4CA8-A16A-E7E04849A4BA}643×293 7.01 KB

2

It sounds like your goal is a filled out manifest.yml, both can achieve what you need.

But this line has be a bit confused as it’s paired with the build steps that are included if you check this box.

Do you want to use a manual Manifest.yml or have VS create one?

3

Eventually, I plan to publish the plug-ins we create in the package manager.

I’m currently looking into Yak and trying to do a test Push.
I’m having trouble with manifest at that stage.

If I can change the manifest entry in VS, I would like to do so.
If I can’t do that, I’m thinking of using a text editor.

First I am thinking of creating a Yak or manifest.yml in VS.

4

This should solve this issue.

5

What specifically doesn’t change what? Only some of the attributes are obtained via yak spec, it doesn’t do Icon and a few others for example. If you’re finding you can’t set manifest properties via the assembly you’ll need to add a step to edit the file or use a manual one.

6

NAME, VERSION, AUTHORS, etc. do not change in VS.
Do these need to be changed in a text editor?

7

In my testing the following assembly properties give the following manifest properties. You shouldn’t need to use a text editor if these are set, it should be automatic.

<AssemblyName> → name: ...
<Version> → version: ...
<Company> → authors: - ...
<description> → description: ...

Some of these properties are obtained from the AssemblyInfo.cs as well.
[assembly: PlugInDescription(DescriptionType.Organization, "Author")] → authors: - ...
[assembly: PlugInDescription(DescriptionType.WebSite, "www.itsmywebsite.com")] → url: ...

8

I see.
I will try that.

9

It seems to be more accurate to put this code in the .csproj file.
However, it seems that “keyword” and “URL” cannot be added.
If you want to specify the details, it seems to be better to set it up from the command prompt through Yak.exe.

  <PropertyGroup>
    <!-- Specifies information for Assembly and Yak -->
    <Version>1.0.0</Version>
    <Title>Title</Title>
    <Company>MyCompany</Company>
    <Description>YakTest</Description>
    <Authors>MyCompany</Authors>
    <Product>RhinoSample</Product>
  </PropertyGroup>
10

Keywords I think you may be right, I’d have to check further. URL comes from the AssemblyInfo.cs