Releases: NetOfficeFw/vbamc
v1.8.0
v1.7.0
This release add new vbamc tool argument to set extended properties in the compiled documents.
Usage
Call vbamc with the argument --property with key value pair PropertyName=Value:
vbamc -m Module.vba -c Class.vba --property Generator=VbaCompiler
This will create extended property named Generator with value VbaCompiler in the compiled Office document.
v1.6.0
This release changes the VbaCompiler to compile the vbaProject.bin and the macro file to output streams instead of files.
Features
- The
VbaCompiler.CompileVbaProject(Stream)will save thevbaProject.bincontent to the stream - The
vbaCompiler.Compile*MacroFile()methods will accept streams
Breaking change
VbaCompilerno longer supports compiling files directly to file path
vbamc tool
- The
vbamctool will generate macro file in correct format based on the file extension
v1.5.1
v1.5.0
This is a release add new API to VbaCompiler to add extended properties to the macro file.
New features
- Add extended properties to the macro file using
VbaCompiler.ExtendedPropertiesproperty
Note
Extended properties are not exposed to the command linevbamctool.
v1.4.3
This is a release with small quality of life changes from @m-kovac.
You can now the the Version property of the add-in file and vbamc compiler and the library can be used in multithreaded scenarios as it won't use write-locks when reading image files for the Ribbon.
New features
- You can set the package version value by the
ProjectVersionargument #7
Improvements
v1.4.2
This release does not have any changes in command line vbamc tool.
Added
- To support compilation of custom addins, the
VbaCompilerlibrary allows the developer to set base directory to Ribbon customization files (thecustomUIfolder). #6 - The
VbaCompilerlibrary was updated to allows compiling PowerPoint add-in files on Windows platform and replacing the user profile path~/with the macOS directory separator. #5
Release notes for v1.4.0
Change the user profile path which will replace the ~/ expression in source code using the --user-profile-path parameter.
Warning Reverted change to the
--fileparameter from v1.3.0 release.
Parameter --file requires filename with extension now. This behavior is the same as for v1.2.0 release.
The vbamc compiler is now listed on NuGet https://www.nuget.org/packages/vbamc
Install it using command
dotnet tool install --global vbamc --version 1.4.1
vbamc v1.4.1
This release does not have any changes in command line vbamc tool.
Added
- The
VbaCompilerlibrary was updated to allows compiling PowerPoint add-in files on Windows platform and replacing the user profile path~/with the macOS directory separator. #5
Release notes for v1.4.0
Change the user profile path which will replace the ~/ expression in source code using the --user-profile-path parameter.
Warning Reverted change to the
--fileparameter from v1.3.0 release.
Parameter --file requires filename with extension now. This behavior is the same as for v1.2.0 release.
The vbamc compiler is now listed on NuGet https://www.nuget.org/packages/vbamc
Install it using command
dotnet tool install --global vbamc --version 1.4.1
vbamc v1.4.0
Change the user profile path which will replace the ~/ expression in source code using the --user-profile-path parameter.
Warning Reverted change to the
--fileparameter from v1.3.0 release.
Parameter --file requires filename with extension now. This behavior is the same as for v1.2.0 release.
The vbamc compiler is now listed on NuGet https://www.nuget.org/packages/vbamc
Install it using command
dotnet tool install --global vbamc --version 1.4.0
vbamc v1.3.0
Change the user profile path which will replace the ~/ expression in source code using the --user-profile-path parameter.
Warning This release changes the behavior of the
--fileparameter.
The vbamc compiler is now listed on NuGet https://www.nuget.org/packages/vbamc
Install it using command
dotnet tool install --global vbamc --version 1.3.0