-
Notifications
You must be signed in to change notification settings - Fork 94
Get D365VisualStudioCompilerResult
Get the compiler outputs presented
Get-D365VisualStudioCompilerResult [[-Module] <String>] [-ErrorsOnly] [-OutputTotals] [-OutputAsObjects]
[[-PackageDirectory] <String>] [<CommonParameters>]
Get the Visual Studio compiler outputs presented in a structured manner on the screen
Get-D365VisualStudioCompilerResult
This will return the compiler output for all modules.
A result set example:
File Warnings Errors
K:\AosService\PackagesLocalDirectory\ApplicationCommon\BuildModelResult.log 55 0 K:\AosService\PackagesLocalDirectory\ApplicationFoundation\BuildModelResult.log 692 0 K:\AosService\PackagesLocalDirectory\ApplicationPlatform\BuildModelResult.log 155 0 K:\AosService\PackagesLocalDirectory\ApplicationSuite\BuildModelResult.log 10916 0 K:\AosService\PackagesLocalDirectory\CustomModule\BuildModelResult.log 1 2
Get-D365VisualStudioCompilerResult -ErrorsOnly
This will return the compiler output for all modules where there was errors in.
A result set example:
File Warnings Errors
K:\AosService\PackagesLocalDirectory\CustomModule\BuildModelResult.log 1 2
Get-D365VisualStudioCompilerResult -ErrorsOnly -OutputAsObjects
This will return the compiler output for all modules where there was errors in. The output will be PSObjects, which can be assigned to a variable and used for futher analysis.
A result set example:
File Warnings Errors
K:\AosService\PackagesLocalDirectory\CustomModule\BuildModelResult.log 1 2
Get-D365VisualStudioCompilerResult -OutputTotals
This will return the compiler output for all modules and write a total overview to the console.
A result set example:
File Warnings Errors
K:\AosService\PackagesLocalDirectory\ApplicationCommon\BuildModelResult.log 55 0 K:\AosService\PackagesLocalDirectory\ApplicationFoundation\BuildModelResult.log 692 0 K:\AosService\PackagesLocalDirectory\ApplicationPlatform\BuildModelResult.log 155 0 K:\AosService\PackagesLocalDirectory\ApplicationSuite\BuildModelResult.log 10916 0 K:\AosService\PackagesLocalDirectory\CustomModule\BuildModelResult.log 1 2
Total Errors: 2 Total Warnings: 11819
Name of the module that you want to work against
Default value is "*" which will search for all modules
Type: String
Parameter Sets: (All)
Aliases: ModuleName
Required: False
Position: 1
Default value: *
Accept pipeline input: False
Accept wildcard characters: FalseInstructs the cmdlet to only output compile results where there was errors detected
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: False
Accept pipeline input: False
Accept wildcard characters: FalseInstructs the cmdlet to output the total errors and warnings after the analysis
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: False
Accept pipeline input: False
Accept wildcard characters: FalseInstructs the cmdlet to output the objects instead of formatting them
If you don't assign the output, it will be formatted the same way as the original output, but without the coloring of the column values
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: False
Accept pipeline input: False
Accept wildcard characters: FalsePath 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: 2
Default value: $Script:PackageDirectory
Accept pipeline input: False
Accept wildcard characters: FalseThis cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters.
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
- Install as a non-Administrator
- Install as a Administrator
- Import d365fo.tools module
- List available commands from d365fo.tools module
- Get help content for a command
- Start, Stop and List services
- Import users into the D365FO environment
- Import external users into the D365FO environment
- Enable users in the D365FO environment
- Update users in the D365FO environment
- Provision D365FO environment to new Azure AD tenant
- Import a bacpac file into a Tier1 environment
- List modules / models
- Compile module
- Install AzCopy
- Install SqlPackage
- Install Nuget
- Speed up LCS download via AzCopy
- Download latest bacpac from LCS via AzCopy
- Register NuGet source
- Configure Azure Logic App
- Fix AzureStorageConfig
- Run a runnable class
- Update users in environment
- Work with Azure Storage Account
- Work with packages, resource label files, language and lables
- Working with the different D365 services