Invoke D365CompilerResultAnalyzer

---

external help file: d365fo.tools-help.xml Module Name: d365fo.tools online version: schema: 2.0.0

Invoke-D365CompilerResultAnalyzer

SYNOPSIS

Analyze the compiler output log

SYNTAX

Invoke-D365CompilerResultAnalyzer [-Path] <String> [[-OutputPath] <String>] [-SkipWarnings] [-SkipTasks]
 [[-PackageDirectory] <String>] [<CommonParameters>]

DESCRIPTION

Analyze the compiler output log and generate an excel file contain worksheets per type: Errors, Warnings, Tasks

It could be a Visual Studio compiler log or it could be a Invoke-D365ModuleCompile log you want analyzed

EXAMPLES

EXAMPLE 1

Invoke-D365CompilerResultAnalyzer -Path "c:\temp\d365fo.tools\Custom\Dynamics.AX.Custom.xppc.log"

This will analyse all compiler output log files generated from Visual Studio. It will use the default path for the OutputPath parameter.

It will build error and error summary worksheets. It will build warning and warning summary worksheets. It will build task and task summary worksheets.

A result set example:

File Filename

---

c:\temp\d365fo.tools\Custom-CompilerResults.xlsx Custom-CompilerResults.xlsx

EXAMPLE 2

Invoke-D365CompilerResultAnalyzer -Path "c:\temp\d365fo.tools\Custom\Dynamics.AX.Custom.xppc.log" -SkipWarnings

This will analyse all compiler output log files generated from Visual Studio. It will use the default path for the OutputPath parameter.

It will build error and error summary worksheets. It will build task and task summary worksheets.

A result set example:

File Filename

---

c:\temp\d365fo.tools\Custom-CompilerResults.xlsx Custom-CompilerResults.xlsx

EXAMPLE 3

Invoke-D365CompilerResultAnalyzer -Path "c:\temp\d365fo.tools\Custom\Dynamics.AX.Custom.xppc.log" -SkipTasks

This will analyse all compiler output log files generated from Visual Studio. It will use the default path for the OutputPath parameter.

It will build error and error summary worksheets. It will build warning and warning summary worksheets.

A result set example:

File Filename

---

c:\temp\d365fo.tools\Custom-CompilerResults.xlsx Custom-CompilerResults.xlsx

PARAMETERS

-Path

Path to the compiler log file that you want to work against

A BuildModelResult.log or a Dynamics.AX.*.xppc.log file will both work

Type: String
Parameter Sets: (All)
Aliases: LogFile

Required: True
Position: 1
Default value: None
Accept pipeline input: True (ByPropertyName, ByValue)
Accept wildcard characters: False

-OutputPath

Path where you want the excel file (xlsx-file) saved to

Type: String
Parameter Sets: (All)
Aliases:

Required: False
Position: 2
Default value: $Script:DefaultTempPath
Accept pipeline input: False
Accept wildcard characters: False

-SkipWarnings

Instructs the cmdlet to skip warnings while analyzing the compiler output log file

Type: SwitchParameter
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: False
Accept pipeline input: False
Accept wildcard characters: False

-SkipTasks

Instructs the cmdlet to skip tasks while analyzing the compiler output log file

Type: SwitchParameter
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: False
Accept pipeline input: False
Accept wildcard characters: False

-PackageDirectory

Path to the directory containing the installed package / module

Default path is the same as the AOS service "PackagesLocalDirectory" directory

Default value is fetched from the current configuration on the machine

Type: String
Parameter Sets: (All)
Aliases:

Required: False
Position: 3
Default value: $Script:PackageDirectory
Accept pipeline input: False
Accept wildcard characters: False

CommonParameters

This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters.

INPUTS

OUTPUTS

NOTES

Tags: Compiler, Build, Errors, Warnings, Tasks

Author: Mötz Jensen (@Splaxi)

This cmdlet is inspired by the work of "Vilmos Kintera" (twitter: @DAXRunBase)

All credits goes to him for showing how to extract these information

His blog can be found here: https://www.daxrunbase.com/blog/

The specific blog post that we based this cmdlet on can be found here: https://www.daxrunbase.com/2020/03/31/interpreting-compiler-results-in-d365fo-using-powershell/

The github repository containing the original scrips can be found here: https://github.com/DAXRunBase/PowerShell-and-Azure

RELATED LINKS