Add Excel and Word Objects support #6
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added support for importing application-specific VBA objects:
ThisWorkbook
(Workbook):ThisWorkbook.cls
or*.wbk.cls
Sheet
(Worksheet):Sheet\d+.cls
(where \d+ matches with any number of digits) or*.sheet.cls
ThisDocument
(Document):ThisDocument.cls
or*.doc.cls
Note that those objects need to be located in subdirectories
/Microsoft Excel Objects
and/Microsoft Word Objects
respectively to be imported. This restriction will be removed when we introduce a manifest file.New utility functions in
Object-Import.ps1
:Parse-Lines
function to strip metadata headers from VBA files before importing.Import-CodeToComponent
,Find-VbaComponent
, and application-specific functions (Import-ExcelObjects
,Import-WordObjects
) to handle importing.Import-ObjectCode
function as a main entry point for importing objects based on the Office application type.