How can file version and product version be defined, when compiling a matlab code to a dll with dotnetbuilder?

47 visualizaciones (últimos 30 días)
The project in deploytool does not take parameters for the produced dll-properties file version, product version. Generated dlls always have a file version of 0.0.0.0.
Any options available to provide version information to the dotnetbuilder output?

Respuesta aceptada

awa
awa el 28 de Nov. de 2018
Editada: awa el 28 de Nov. de 2018
The way we build dotnet dlls with version info nowadays, is to not use the project files but the mcc compiler on the command line / script and include an Assemblyinfo.cs -file as C# -code created by the build script including the version information. The full filename of AssemblyInfo.cs is added to the mcc command line.
This is also working if you add an appropriate AssemblyInfo.cs as an additional parameter passed to MCC. Just tried on an older project.
DeploytoolSettings.png
  5 comentarios
Jose Maria Lorenzo
Jose Maria Lorenzo el 10 de Feb. de 2023
Facing the same issue, any update on this?? Properly working for standard dll but for .NET native file it does not work ( working on 2016B ).

Iniciar sesión para comentar.

Más respuestas (2)

Richa Gupta
Richa Gupta el 20 de Jul. de 2015
Hi Awa,
It is possible to provide version of the .NET DLL generated using MATLAB Compiler. You can do this using the "Library version" field in deploytool. For more information, you can refer to the following link:
As you can see, you can view and change the version number under the Application Information section.
Also, what do you mean by specifying the product version for a DLL?
-Richa
  3 comentarios
Morris Maynard
Morris Maynard el 11 de Mayo de 2018
Editada: Morris Maynard el 11 de Mayo de 2018
The answer does not work. If I "view and change version number under the Application Information section" (by the way, the linked page does not mention this or show it as a possibility) it does not change the version number of the .Net dll. The .Net assembly version is very important and is always in the format w.x.y.z, where wxy and z are numbers. Whatever the version number specified in the Settings menu it, it won't allow input in this format.
Girija Jarvis
Girija Jarvis el 27 de Nov. de 2018
If you have by now learnt how to version the .net assembly version please can you share the details with me, i am unable to version the .net dll either

Iniciar sesión para comentar.


Ralph Coleman
Ralph Coleman el 31 de En. de 2020
Editada: Ralph Coleman el 31 de En. de 2020
From MATLAB R2019b, the solution using an "AssemblyInfo.cs" file containing the AssemblyVersion attribute causes a compilation error.
Instead, now enter directly the library version in the suitable field of the Library Compiler tool as shown below.
Note that 4 digit versions are now accepted (whereas only two digits were accepted in previous versions).
However, the other attributes in "AssemblyInfo.cs" can still be used as in the example code below:
using System.Reflection;
[assembly: AssemblyCopyright("Copyright © 2020")]
[assembly: AssemblyProduct("DemoToolCore")]
[assembly: AssemblyInformationalVersion("2.5alpha")]
Note the absence of AssemblyVersion and AssemblyFileVersion attributes - the latter does not cause a compilation error but overwrites the library version given in the field above, so it is to be avoided.
The result obtained is the following:

Categorías

Más información sobre Deploy to .NET Applications Using MWArray API en Help Center y File Exchange.

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by