Issues with current release / build pipeline

[f00f]

This list is to summarize all things which went wrong with the latest release (v.11.0).
All are minor issues which are no regression, but would be nice if they were fixed.

• Tag is not created (investigate build output)
• Failure e-mails are not sent (empty recipients list)
• netstandard assemblies have version number 1.0 (wait for and copy fix in Util)
• OrbbecOpenNI and WebCam (C++/CLI) do not show any version number in Explorer/Properties dialog (wait for and adapt fix in Util)
• No .pdb files are deployed to Release (the build config) folders fixed in Deploy .pdb files to release (the build config) folders, too #100
• TI Voxel is not deployed fixed in Deploy TI Voxel and dependencies. #111

[f00f]

Log output regarding the Tag

%>echo Tagging the Git Repository ... 
Tagging the Git Repository ...

%>"Scripts\Create Git Release Tag.bat" v.11.0.0.117 
Creating Git Tag for release:
    Remote:   origin
    Tag:      v.11.0.0.117
    Message:  Release v.11.0.0.117 (2018-02-23 17.44)
bash: /dev/tty: No such device or address
error: failed to execute prompt script (exit code 1)
fatal: could not read Username for 'https://github.com': Invalid argument

[f00f]

I have created the tag manually for this release.

[jangernert]

Regarding the missing meta data of the C++/Cli binaries:

The 'Details' page in Windows Explorer is pulling the information from unmanaged structures in the file, so you'll need to create an unmanaged version resource in order to fill that in.

So in the file app.rc add a new resource Version in which the information can be filled in. However, I am not sure how to reference the version number from SolutionAssemblyInfo.h there.

edit: There seems to be a tool that eases the process

[jangernert]

Version Number 1.0 of netstandard binaries:
The file AssemblyInfo.cs is explicitly removed from the project.

  <ItemGroup>
    <Compile Remove="Properties\AssemblyInfo.cs" />
    <Compile Remove="Properties\Resources.Designer.cs" />
  </ItemGroup>

I'm not entirely sure why that is. After clarifying that we could potentially revert that change.

[f00f]

C++/CLI: yep, we need to add this resource crap

netstandard: cannot handle AssemblyInfo files (I think it complains about duplicate stuff - you can try it locally. the version needs to be in the project file (see Util for reference)

Both are issues which could best be addressed by a script which reads the version number from a file and patches all the rest. Ideally the build job should also be able to parse that file.